Use configure-aws-credentials workflow instead of passing `secret_a…

…ccess_key` (valkey-io#1363) This PR fixes valkey-io#1346 where we can get rid of the long term credentials by using OpenID Connect. OpenID Connect (OIDC) allows your GitHub Actions workflows to access resources in Amazon Web Services (AWS), without needing to store the AWS credentials as long-lived GitHub secrets. --------- Signed-off-by: vudiep411 <[email protected]>
Autxmaton · Dec 15, 2024 · dc4e0a1 · dc4e0a1
1 parent 8f18f8a
commit dc4e0a1
Show file tree

Hide file tree

Showing 4 changed files with 0 additions and 265 deletions.
diff --git a/.github/workflows/build-release-packages.yml b/.github/workflows/build-release-packages.yml
diff --git a/.github/workflows/call-build-linux-arm-packages.yml b/.github/workflows/call-build-linux-arm-packages.yml
diff --git a/.github/workflows/call-build-linux-x86-packages.yml b/.github/workflows/call-build-linux-x86-packages.yml
diff --git a/.github/workflows/trigger-valkey-container.yml b/.github/workflows/trigger-valkey-container.yml