chore: wire secrets to Bitwarden Secrets Manager in CI - #174
Merged
Conversation
Contributor
🚀 Preview of AdvancedShopFinder📦 Preview JARAvailable for 7 days (until 2026-08-08)
📖 Documentation & ReportsAvailable for 7 days (until 2026-08-08)
🧪 Test Summary
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
AWS_ACCESS_KEY_ID/AWS_SECRET_ACCESS_KEYfrom Bitwarden Secrets Manager (BSM) viabitwarden/sm-action@v2inpreview.yml'supload-s3job, using the org-levelNIKOMARU_BITWARDEN_SECRET_MANAGER_ACCESS_TOKENsecret, instead of GitHub repo secrets.S3_UPLOAD_BUCKET/S3_ENDPOINTstay as GitHub secrets (not in BSM). This repo has no Pelican deploy workflow.Test plan
preview.yml(upload-s3job) succeeds on the next PR preview run