[fleet] add support for inline json to --stages argument in CLI

[serbrech]

fixes #8979

---

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

Related command

az fleet

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
⚠️ 1009 - ParaPropRemove	fleet updaterun create	cmd fleet updaterun create update parameter stages: removed property type=file_type
⚠️ 1009 - ParaPropRemove	fleet updatestrategy create	cmd fleet updatestrategy create update parameter stages: removed property type=file_type

[azure-client-tools-bot-prd]

Hi @serbrech,
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.

[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>

[yonzhan]

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

[Copilot]

Pull Request Overview

This PR adds support for inline JSON strings to the --stages argument in Azure fleet CLI commands, allowing users to provide stage configuration either as a file path or as inline JSON content.

Key Changes

• Modified parameter handling to accept both file paths and inline JSON strings for the --stages argument
• Updated the core parsing logic to detect whether input is a file path or JSON string
• Added comprehensive test coverage for the new inline JSON functionality

Reviewed Changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 2 comments.

File	Description
src/fleet/azext_fleet/_params.py	Updated parameter definitions to remove file type restrictions and clarify help text for inline JSON support
src/fleet/azext_fleet/custom.py	Modified get_update_run_strategy function to handle both file paths and inline JSON strings
src/fleet/azext_fleet/tests/latest/test_stages_json.py	Added comprehensive test suite covering file path, inline JSON, and error scenarios

Comments suppressed due to low confidence (1)

src/fleet/azext_fleet/tests/latest/test_stages_json.py:252

• [nitpick] Consider adding test cases for other error scenarios such as missing required fields (e.g., missing 'stages' key, missing 'name' in stage/group) to ensure robust error handling.

        invalid_json = '{"stages": [{"name": "test", invalid_syntax}]}'

[github-actions]

Hi @serbrech

⚠️ Release Requirements

Module: fleet

• ⚠️ Please update VERSION to be 1.7.0 in src/fleet/setup.py

Notes

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

[serbrech]

@kairu-ms happy to merge this after your review

[serbrech]

/azp run

[azure-pipelines]

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

[kairu-ms]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 2 pipeline(s).

[serbrech]

@copilot

• Update VERSION to "1.6.1" in src/fleet/setup.py
• log the update in src/fleet/HISTORY.rstas : "Modified parameter handling to accept both file paths and inline JSON strings for the --stages argument"

[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).

[kairu-ms]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 2 pipeline(s).

[azclibot]

[Release] Update index.json for extension [ fleet-1.6.1 ] : https://dev.azure.com/msazure/One/_build/results?buildId=132232791&view=results