[v10] Refactor Drone Pipelines to use AWS role assumption#17244
Merged
Conversation
These are reversed in master/v11 (ecr first, and then quay) and having the order consisten across branches will make future ports easier.
Backports #17201 Contributes to gravitational/SecOps#213
wadells
changed the title
github-actions
Bot
requested review from
fheinecke,
justinas,
r0mant and
reedloden
reedloden
approved these changes
Oct 10, 2022
r0mant
approved these changes
Oct 10, 2022
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
3 participants
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.
Backports #17201
Contributes to https://github.com/gravitational/SecOps/issues/213
There was a single merge conflict, caused by the ecr/quay promotion pipelines having a different order in v10 than in master/v11. I updated v10 to match master/v11, to make future porting easier and consistent. See 6a3f802
Testing Done
Since there was some mergeing I re-verified instead of trusting the results from master. Both tag and promote look good!