add Fleet API 2025-03-01 #8589
add Fleet API 2025-03-01 #8589
Conversation
|
Hi @frantran, |
|
| rule | cmd_name | rule_message | suggest_message |
|---|---|---|---|
| fleet autoupgradeprofile create | cmd fleet autoupgradeprofile create removed property is_preview |
||
| fleet autoupgradeprofile delete | cmd fleet autoupgradeprofile delete removed property is_preview |
||
| fleet autoupgradeprofile generate-update-run | cmd fleet autoupgradeprofile generate-update-run added |
||
| fleet autoupgradeprofile list | cmd fleet autoupgradeprofile list removed property is_preview |
||
| fleet autoupgradeprofile show | cmd fleet autoupgradeprofile show removed property is_preview |
||
| fleet autoupgradeprofile wait | cmd fleet autoupgradeprofile wait removed property is_preview |
|
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>
|
|
/azp run |
|
Azure Pipelines successfully started running 2 pipeline(s). |
|
|
/azp run |
|
Azure Pipelines successfully started running 2 pipeline(s). |
There was a problem hiding this comment.
Is this file meant to be deleted? Maybe you used git mv instead of git cp.
There was a problem hiding this comment.
all files under src/fleet/azext_fleet/vendored_sdks/v2024_05_02_preview/* are meant to be deleted, as that is the "older" version
There was a problem hiding this comment.
Ahh, the list of changed files makes it look like this one file only has been deleted, but I see now that all the others are gone as well. They just show as renamed instead of deleted.
|
/azp run |
|
Azure Pipelines successfully started running 2 pipeline(s). |
|
/azp run |
|
Commenter does not have sufficient privileges for PR 8589 in repo Azure/azure-cli-extensions |
|
/azp run |
|
Azure Pipelines successfully started running 2 pipeline(s). |
|
/azp run |
|
Azure Pipelines successfully started running 2 pipeline(s). |
|
/azp run |
|
Azure Pipelines successfully started running 2 pipeline(s). |
|
/azp run |
|
Commenter does not have sufficient privileges for PR 8589 in repo Azure/azure-cli-extensions |
|
/azp run |
|
Azure Pipelines successfully started running 2 pipeline(s). |
|
/azp run |
|
Azure Pipelines successfully started running 2 pipeline(s). |
This checklist is used to make sure that common guidelines for a pull request are followed.
Related command
az fleet ...az fleet autoupgadeprofile genenerate-update-run ...2025-03-01General 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.