Restore Cache from S3 Step Settings
This topic provides settings for the Restore Cache from S3 step.
In this topic:
- AWS Connector
- Endpoint URL
- Archive Format
- Path Style
- Fail if Key Doesn't exist
- Run as User
- Set container resources
- See Also
The unique name for this step.
The Harness Connector to use when restoring the cache from AWS S3.
Typically, this is the same Connector used when you saved the cache.
The AWS IAM roles and policies associated with the account used in the Harness AWS Connector must be able to read from S3.
An AWS region you used when you saved the cache.
The AWS S3 bucket you used when you saved the cache.
The key you used to identify the cache when you saved it.
Endpoint URL for S3-compatible providers (not needed for AWS).
Select the archive format.
Select whether to use Virtual Hosted Style (http://bucket.host/key) or Path Style (http://host/bucket/key). For MinIO, use Path Style (True).
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.