Gitea/cache
1
0
Fork 0
mirror of https://github.com/actions/cache.git synced 2025-10-31 11:48:38 +08:00
Code Issues Actions Packages Projects Releases Wiki Activity

Allow to use existing AWS credentials even on RunsOn, by setting RUNS_ON_RUNNER_NAME=""

Browse Source
This commit is contained in:
Cyril Rohr 2024-05-21 16:52:36 +00:00
parent c416bffd71
commit cf6e7f2371
2 changed files with 2 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
README.md
View File

@ -42,5 +42,6 @@ Be aware of S3 transfer costs if your runners are not in the same AWS region as
## Special environment variables
* `RUNS_ON_S3_BUCKET_CACHE`: if set, the action will use this bucket to store the cache.
* `RUNS_ON_RUNNER_NAME`: if set to `""` and running from RunsOn, the action will not ignore AWS credentials from the environment, if any.
* `RUNS_ON_S3_FORCE_PATH_STYLE` or `AWS_S3_FORCE_PATH_STYLE`: if one of those environment variables equals the string `"true"`, then the S3 client will be configured to force the path style.

2
src/custom/backend.ts
View File

@ -26,7 +26,7 @@ export interface ArtifactCacheEntry {
// if executing from RunsOn, unset any existing AWS env variables so that we can use the IAM instance profile for credentials
// see unsetCredentials() in https://github.com/aws-actions/configure-aws-credentials/blob/v4.0.2/src/helpers.ts#L44
if (process.env.RUNS_ON_RUNNER_NAME) {
if (process.env.RUNS_ON_RUNNER_NAME && process.env.RUNS_ON_RUNNER_NAME !== "") {
delete process.env.AWS_ACCESS_KEY_ID;
delete process.env.AWS_SECRET_ACCESS_KEY;
delete process.env.AWS_SESSION_TOKEN;