fix: Modified yaml file to use secrets instead of variables#111
Merged
Roopan-Microsoft merged 2 commits intomainfrom Mar 4, 2026
Merged
fix: Modified yaml file to use secrets instead of variables#111Roopan-Microsoft merged 2 commits intomainfrom
Roopan-Microsoft merged 2 commits intomainfrom
Conversation
fUpdated Azure credentials to use secrets for security.
Prajwal-Microsoft
requested review from
Avijit-Microsoft,
Roopan-Microsoft,
Vinay-Microsoft,
aniaroramsft and
dgp10801
as code owners
Roopan-Microsoft
approved these changes
Mar 4, 2026
|
🎉 This PR is included in version 1.2.3 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
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
2 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.
Purpose
This pull request updates the way sensitive Azure credentials are provided to the template validation workflow. Instead of using GitHub repository variables, the workflow now uses GitHub secrets for these credentials, which is a more secure practice.
Security improvements:
AZURE_CLIENT_ID,AZURE_TENANT_ID, andAZURE_SUBSCRIPTION_IDin.github/workflows/azd-template-validation.ymlto use GitHub secrets instead of repository variables, enhancing the security of credential management.Does this introduce a breaking change?
Golden Path Validation
Deployment Validation
What to Check
Verify that the following are valid
Other Information