[fleet] Mark Gate commands as preview.

[dvadas]

---

This checklist is used to make sure that common guidelines for a pull request are followed.

Related command

az fleet gate ...

General Guidelines

• Have you run azdev style <YOUR_EXT> locally? (pip install azdev required)
• Have you run python scripts/ci/test_index.py -q locally? (pip install wheel==0.30.0 required)
• My extension version conforms to the Extension version schema

For new extensions:

• My extension description/summary conforms to the Extension Summary Guidelines.

About Extension Publish

There is a pipeline to automatically build, upload and publish extension wheels.
Once your pull request is merged into main branch, a new pull request will be created to update src/index.json automatically.
You only need to update the version information in file setup.py and historical information in file HISTORY.rst in your PR but do not modify src/index.json.

[azure-client-tools-bot-prd]

⚠️Azure CLI Extensions Breaking Change Test

⚠️fleet

rule	cmd_name	rule_message	suggest_message
⚠️ 1003 - CmdPropAdd	fleet gate approve	cmd fleet gate approve added property is_preview
⚠️ 1003 - CmdPropAdd	fleet gate list	cmd fleet gate list added property is_preview
⚠️ 1003 - CmdPropAdd	fleet gate show	cmd fleet gate show added property is_preview
⚠️ 1003 - CmdPropAdd	fleet gate update	cmd fleet gate update added property is_preview

[azure-client-tools-bot-prd]

Hi @dvadas,
Please write the description of changes which can be perceived by customers into HISTORY.rst.
If you want to release a new extension version, please update the version in setup.py as well.

[Copilot]

Pull Request Overview

This PR marks the Azure Fleet Gate commands as preview in the Azure CLI extension. The change adds the is_preview=True parameter to the command group definition to indicate that these commands are in preview status.

• Adds preview flag to the fleet gate command group

[yonzhan]

Thank you for your contribution! We will review the pull request and get back to you soon.

[github-actions]

The git hooks are available for azure-cli and azure-cli-extensions repos. They could help you run required checks before creating the PR.

Please sync the latest code with latest dev branch (for azure-cli) or main branch (for azure-cli-extensions).
After that please run the following commands to enable git hooks:

pip install azdev --upgrade
azdev setup -c <your azure-cli repo path> -r <your azure-cli-extensions repo path>

[github-actions]

Hi @dvadas

Release Suggestions

Module: fleet

• Update VERSION to 1.7.0 in src/fleet/setup.py

Notes

• For more info about extension versioning, please refer to Extension version schema

[serbrech]

@kairu-ms we don't want this change to trigger a release. it's ok to bundle it with other changes that are coming.
how do we deal with the version requirement in that case?

[kairu-ms]

Only bump up this version number will trigger a release. So please remove this line change

[kairu-ms]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 2 pipeline(s).

[yonzhan]

Please fix CI issues

[dvadas]

/azp run

[azure-pipelines]

Commenter does not have sufficient privileges for PR 9081 in repo Azure/azure-cli-extensions

[kairu-ms]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 2 pipeline(s).

[kairu-ms]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 2 pipeline(s).