Restore Cache from GCS Settings
This topic provides settings for the Restore Cache from GCS step.
The Restore Cache from GCS step restores files and directories that were saved using the Save Cache to GCS step.
In this topic:
- GCP Connector
- Archive Format
- Fail if Key Doesn't exist
- Run as User
- Set container resources
- See Also
The unique name for this step.
The Harness Connector for the GCP account where you saved the cache.
GCS bucket name.
The key used to identify the cache.
Select the archive format.
Fail if Key Doesn't exist
Select this option to fail the step if the key doesn’t exist.
Run as User
Set the value to specify the user id for all processes in the pod, running in containers. See Set the security context for a pod.
Set container resources
Maximum resources limit values for the resources used by the container at runtime.
Maximum memory that the container can use.
You can express memory as a plain integer or as a fixed-point number using one of these suffixes: G, M.
You can also use the power-of-two equivalents: Gi, Mi.
Limit the number of cores that the container can use.
Limits for CPU resources are measured in cpu units.
Fractional requests are allowed. The expression 0.1 is equivalent to the expression 100m, that can be read as one hundred millicpu.
Timeout for the step. Once the timeout is reached, the step fails, and the Pipeline execution continues.