[providerhub] Add command example

[cxznmhdcxz]

---

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

Related command

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

️✔️Non Breaking Changes

[azure-client-tools-bot-prd]

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

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

[Copilot]

Pull Request Overview

This PR adds a command usage example to the providerhub sku nested-resource-type-third create command documentation to improve user guidance.

• Adds an example section to the command's docstring showing how to create a SKU with nested resource types

[Copilot]

The JSON in the --sku-settings parameter is malformed. Property names should be quoted. The correct format should be: --sku-settings "[{"name":"freeSku","tier":"Tier1","kind":"Standard"},{"name":"premiumSku","tier":"Tier2","kind":"Premium","costs":[{"meter-id":"xxx"}]}]"

Suggested change

az providerhub sku nested-resource-type-third create --provider-namespace Microsoft.Contoso --resource-type testResourceType --nested-resource-type-first nestedResourceTypeFirst --nested-resource-type-second nestedResourceTypeSecond --nested-resource-type-third nestedResourceTypeThird --name testSku --sku-settings "[{name:freeSku,tier:Tier1,kind:Standard},{name:premiumSku,tier:Tier2,kind:Premium,costs:[{meter-id:xxx}]}]"

az providerhub sku nested-resource-type-third create --provider-namespace Microsoft.Contoso --resource-type testResourceType --nested-resource-type-first nestedResourceTypeFirst --nested-resource-type-second nestedResourceTypeSecond --nested-resource-type-third nestedResourceTypeThird --name testSku --sku-settings "[{\"name\":\"freeSku\",\"tier\":\"Tier1\",\"kind\":\"Standard\"},{\"name\":\"premiumSku\",\"tier\":\"Tier2\",\"kind\":\"Premium\",\"costs\":[{\"meter-id\":\"xxx\"}]}]"

[github-actions]

CodeGen Tools Feedback Collection

Thank you for using our CodeGen tool. We value your feedback, and we would like to know how we can improve our product. Please take a few minutes to fill our codegen survey

[github-actions]

Hi @cxznmhdcxz

Release Suggestions

Module: providerhub

• Please log updates into to src/providerhub/HISTORY.rst
• Update VERSION to 1.0.0b3 in src/providerhub/setup.py

Notes

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