Skip to content

[azd.ai.toolboxs] allow azd deploy to skip deploying a new toolbox version #9023

Description

@huimiu

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

  • Detect the currently deployed toolbox version before deploying.
  • Skip toolbox deployment when the version is already current.
  • Expose a flag or config to control the skip behavior.
  • Add unit/integration tests covering the skip logic.
  • Update documentation and help text as needed.

Notes

  • Consider CI/CD scenarios where users want deterministic, idempotent deployments.
  • Ensure --no-prompt / non-interactive mode works correctly with the skip logic.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or improvement

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions