Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ci(fix): Use OIDC auth to login on ECR #10055

Merged
merged 5 commits into from
Dec 12, 2024
Merged

ci(fix): Use OIDC auth to login on ECR #10055

merged 5 commits into from
Dec 12, 2024

Conversation

rahulinux
Copy link
Contributor

Problem

CI currently uses static credentials in some places. These are less secure and hard to maintain, so we are going to deprecate them and use OIDC auth.

Summary of changes

  • ci(fix): Use OIDC auth to upload artifact on s3
  • ci(fix): Use OIDC auth to login on ECR

@rahulinux rahulinux requested a review from a team as a code owner December 9, 2024 11:25
Copy link
Member

@bayandin bayandin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM if it works 😄
We also have a bunch of AWS_ACCESS_KEY_DEV usage in other workflows:

.github/workflows/_build-and-test-locally.yml:  AWS_ACCESS_KEY_ID: ${{ secrets.AWS_ACCESS_KEY_DEV }}
.github/workflows/cloud-regress.yml:      AWS_ACCESS_KEY_ID: ${{ secrets.AWS_ACCESS_KEY_DEV }}
.github/workflows/neon_extra_builds.yml:          AWS_ACCESS_KEY_ID: ${{ secrets.AWS_ACCESS_KEY_DEV }}
.github/workflows/periodic_pagebench.yml:        AWS_ACCESS_KEY_ID: ${{ secrets.AWS_ACCESS_KEY_DEV }}
.github/workflows/pg-clients.yml:  AWS_ACCESS_KEY_ID: ${{ secrets.AWS_ACCESS_KEY_DEV }}
.github/workflows/pin-build-tools-image.yml:          username: ${{ secrets.AWS_ACCESS_KEY_DEV }}

Copy link

github-actions bot commented Dec 9, 2024

No tests were run or test report is not available

Test coverage report is not available

The comment gets automatically updated with the latest test results
00900ca at 2024-12-09T12:05:51.289Z :recycle:

@rahulinux
Copy link
Contributor Author

LGTM if it works 😄 We also have a bunch of AWS_ACCESS_KEY_DEV usage in other workflows:

.github/workflows/_build-and-test-locally.yml:  AWS_ACCESS_KEY_ID: ${{ secrets.AWS_ACCESS_KEY_DEV }}
.github/workflows/cloud-regress.yml:      AWS_ACCESS_KEY_ID: ${{ secrets.AWS_ACCESS_KEY_DEV }}
.github/workflows/neon_extra_builds.yml:          AWS_ACCESS_KEY_ID: ${{ secrets.AWS_ACCESS_KEY_DEV }}
.github/workflows/periodic_pagebench.yml:        AWS_ACCESS_KEY_ID: ${{ secrets.AWS_ACCESS_KEY_DEV }}
.github/workflows/pg-clients.yml:  AWS_ACCESS_KEY_ID: ${{ secrets.AWS_ACCESS_KEY_DEV }}
.github/workflows/pin-build-tools-image.yml:          username: ${{ secrets.AWS_ACCESS_KEY_DEV }}

sure, will update those as well. might need to create follow-up if something breaks.

@rahulinux rahulinux force-pushed the ci/use-oidc-auth branch 15 times, most recently from 998d6ea to 000081f Compare December 11, 2024 19:17
@rahulinux rahulinux enabled auto-merge December 12, 2024 15:11
@rahulinux rahulinux added this pull request to the merge queue Dec 12, 2024
Merged via the queue into main with commit 58d45c6 Dec 12, 2024
91 of 92 checks passed
@rahulinux rahulinux deleted the ci/use-oidc-auth branch December 12, 2024 15:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants