fix(ci-lease): reorder template fetch + S3 perm#405
Merged
Conversation
S3 fallback was using anonymous curl which got 403. The bucket isn't public. Switch to 'aws s3 cp' with the hub creds (ci-lease role) and add s3:GetObject permission on the blueprints bucket's scenarios/*/template.yaml keys. Reorder: configure-aws-credentials (hub) now runs BEFORE Resolve template path so the aws s3 cp call has creds.
chrisns
had a problem deploying
to
smoke-test-deploy
GitHub Actions
Failure
chrisns
had a problem deploying
to
smoke-test-deploy
GitHub Actions
Failure
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.
S3 fallback needs IAM creds — reorder + grant s3:GetObject.