ci: update EXP input handling in deployment workflows #738
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
Vamshi-Microsoft
requested review from
Avijit-Microsoft,
Prajwal-Microsoft,
Roopan-Microsoft,
Vinay-Microsoft,
aniaroramsft,
brittneek,
dgp10801,
nchandhi and
toherman-msft
as code owners
Prajwal-Microsoft
approved these changes
Jan 19, 2026
Contributor
|
🎉 This PR is included in version 3.17.5 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
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.
Purpose
This pull request makes minor adjustments to the GitHub Actions workflow files related to deployment. The changes focus on how the
EXP_ENABLEDflag is handled and passed between jobs.Workflow configuration updates:
.github/workflows/deploy-orchestrator.yml, theexpparameter is now sourced from workflow inputs rather than from the outputs of thedeployjob, making the workflow more flexible and consistent with other input parameters..github/workflows/job-azure-deploy.yml, theEXP_ENABLEDoutput and its associated description have been removed, as it is no longer needed due to the change above.Does this introduce a breaking change?
Golden Path Validation
Deployment Validation