-
Notifications
You must be signed in to change notification settings - Fork 1.5k
[managementpartner] Add command example #8998
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
[managementpartner] Add command example #8998
Conversation
|
Validation for Breaking Change Starting...
Thanks for your contribution! |
|
Hi @cxznmhdcxz, |
|
Thank you for your contribution! We will review the pull request and get back to you soon. |
|
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). pip install azdev --upgrade
azdev setup -c <your azure-cli repo path> -r <your azure-cli-extensions repo path>
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR adds a command example to the managementpartner extension and updates the minimum CLI core version requirement. The primary purpose is to improve documentation by providing users with a concrete usage example for the az managementpartner create command.
Key changes:
- Added a practical command example showing how to create a management partner association
- Updated minimum CLI core version from 2.61.0 to 2.75.0
Reviewed Changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| azext_metadata.json | Updated minimum CLI core version requirement to 2.75.0 |
| _create.py | Added command example to the docstring for the Create class |
| class Create(AAZCommand): | ||
| """Associates a Microsoft Partner Network(MPN) ID to the current authenticated user or service principal. | ||
| :example: Associates a Microsoft Partner Network(MPN) ID to the current authenticated user or service principal. |
Copilot
AI
Jul 24, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[nitpick] The example description repeats the class docstring. Consider making it more specific, such as ':example: Create a management partner association with MPN ID 123456'
| :example: Associates a Microsoft Partner Network(MPN) ID to the current authenticated user or service principal. | |
| :example: Create a management partner association with MPN ID 123456. |
CodeGen Tools Feedback CollectionThank 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 |
|
Hi @cxznmhdcxz Release SuggestionsModule: managementpartner
Notes
|
|
/azp run |
|
Azure Pipelines will not run the associated pipelines, because the pull request was updated after the run command was issued. Review the pull request again and issue a new run command. |
|
/azp run |
|
Azure Pipelines will not run the associated pipelines, because the pull request was updated after the run command was issued. Review the pull request again and issue a new run command. |
aaz Azure/aaz#818
This checklist is used to make sure that common guidelines for a pull request are followed.
Related command
General Guidelines
azdev style <YOUR_EXT>locally? (pip install azdevrequired)python scripts/ci/test_index.py -qlocally? (pip install wheel==0.30.0required)For new extensions:
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.jsonautomatically.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.