Fix: Ensure azd up -e deploys resources to the specified environment, ignoring the default environment
#4561
Conversation
Menghua1
requested review from
ellismg,
wbreza,
vhvb1989,
hemarina and
weikanglim
as code owners
| stepArgs := append(step.AzdCommand.Args, "-e", envValue) | ||
| step.AzdCommand.Args = stepArgs | ||
| } | ||
| } |
There was a problem hiding this comment.
Since -e is a global flag, we should not manually set it like this. It should be already visible to all commands.
There was a problem hiding this comment.
@vhvb1989 Thanks for your feedback!
When debugging the azd up -e <environment> command, we found that the actual executed steps (such as azd package, azd provision, and azd deploy) did not include the -e flag, which caused these commands to use the default environment instead of the environment specified by the user through -e. To ensure that these subcommands can correctly use the environment specified by -e, I manually set it in the code.
If you think there is a better solution, you are welcome to discuss further in the issue #4411 (comment)!
There was a problem hiding this comment.
The current solution wouldn't work if the user added the workflow step to reference an azd command not accepting -e. An immediate solution doesn't come to mind, but will require some additional team discussion.
Fix issue#4411.
@rajeshkamal5050 for notification.