Scope azd deployment job to a GitHub Environment - #90
Closed
Arun Sekhar (achandmsft) wants to merge 1 commit into
Closed
Scope azd deployment job to a GitHub Environment#90Arun Sekhar (achandmsft) wants to merge 1 commit into
Arun Sekhar (achandmsft) wants to merge 1 commit into
Conversation
Collaborator
Author
|
Closing in favor of #91, which removes the unused AZURE_CREDENTIALS reference at the root instead of scoping the job to an environment. |
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
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.
Binds the azd deployment job in
azure-dev.yamlto a GitHubproductionEnvironment.Scoping the deploy job to an Environment lets deployment configuration be managed through environment protection rules (required reviewers, branch/tag restrictions, wait timers) and keeps deployment-time configuration grouped per environment. This aligns with the recommended
azdCI/CD pipeline setup.No workflow logic changes - only adds
environment: productionto thebuildjob.