Summary
Track and implement the ability for azd deploy to skip deploying a new toolbox version when one is already present and up-to-date.
Motivation
Currently, azd deploy always deploys the toolbox version as part of the deployment process. There should be a mechanism to skip this step when the existing toolbox version satisfies the requirements, reducing unnecessary deployment time and resource usage.
Proposed Behavior
- When running
azd deploy, detect whether the currently deployed toolbox version is already at the desired version.
- If the version matches (or satisfies a version constraint), skip the toolbox deployment step.
- Provide a flag or configuration option (e.g.,
--skip-toolbox-update) to explicitly opt in/out of this behavior.
Acceptance Criteria
Notes
- Consider CI/CD scenarios where users want deterministic, idempotent deployments.
- Ensure
--no-prompt / non-interactive mode works correctly with the skip logic.
Summary
Track and implement the ability for
azd deployto skip deploying a new toolbox version when one is already present and up-to-date.Motivation
Currently,
azd deployalways deploys the toolbox version as part of the deployment process. There should be a mechanism to skip this step when the existing toolbox version satisfies the requirements, reducing unnecessary deployment time and resource usage.Proposed Behavior
azd deploy, detect whether the currently deployed toolbox version is already at the desired version.--skip-toolbox-update) to explicitly opt in/out of this behavior.Acceptance Criteria
Notes
--no-prompt/ non-interactive mode works correctly with the skip logic.