Fix production deployments failing due to missing -global suffix in staging registry reference #803
Conversation
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
Co-authored-by: Thomas Jespersen <tje@platformplatform.net>
|
tjementum
deleted the
pp-667-fix-missing-global-suffix-in-staging-registry-id-for
branch
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.
Summary & Motivation
Fix production container deployments failing to import images from the staging registry. The
STAGING_REGISTRY_IDin_deploy-container.ymlwas missing the-globalsuffix in the resource group name, a bug introduced in #793 when the global resource group was renamed. This is currently preventing all deployments to production.{prefix}-stageto{prefix}-stage-globalto match the actual location of the staging container registryChecklist