Use INT E2E Creds in Prod pipeline as we pull from the INT image registry and spin up our resources in our INT sub #1954
Conversation
This file contains 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
…stry and spin up our resources in our INT sub
bennerv
requested review from
ross-bryan,
hawkowl,
jewzaam,
m1kola,
mwoodson,
petrkotas and
rogbas
as code owners
petrkotas
approved these changes
Feb 9, 2022
ross-bryan
approved these changes
Feb 9, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Which issue this PR addresses:
We incorrectly used a wrong variable group in our updated pipelines. Our e2e for prod spins up a cluster in our INT sub as well as pulls from the INT Azure Container Registry.
What this PR does / why we need it:
Fixes e2e for prod.
Test plan for issue:
Run and done
Is there any documentation that needs to be updated for this PR?
Not specifically for this PR