-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Adding 2024-04-10 api version fior AzureLargeInstance #7690
Adding 2024-04-10 api version fior AzureLargeInstance #7690
Conversation
️✔️Azure CLI Extensions Breaking Change Test
|
Hi @8Gitbrix, |
Thank you for your contribution! We will review the pull request and get back to you soon. |
For more info about extension versioning, please refer to Extension version schema |
For some reason the tests are failing. They were failing in the first commit since the resources I was previously using were deleted. I've since updated them and tested the commands individually. Can someone help me understand how the tests are still failing? |
When running
|
What version of pytest is needed? This is confusing. aaz-dev requires pytest 6.2.0,. But when downgrading, it complains that pytest-xdist package requires pytest 7.0.0 or higher... |
Was able to get tests running on mac by exporting this flag Also Azure/aaz#493 for the previous api version needs to be merged |
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 |
/azp run |
Azure Pipelines successfully started running 2 pipeline(s). |
Hi @8Gitbrix, please fix these lint issues https://dev.azure.com/azclitools/public/_build/results?buildId=168363&view=logs&j=e2e497a5-ba27-5eb9-f39e-d929d56974a6&t=61cc2d02-f6f4-5007-71e9-5651933c3fe7&l=167 Please verify the following breaking change is by design or not.
|
Hi @8Gitbrix, if the following breaking changes are by design, please update the release notes for them. Thanks.
|
@kairu-ms Thanks for catching that. There shouldn't be any breaking changes. I corrected the parameter names for those methods. Let me know if there's any other things I've missed. |
src/azurelargeinstance/azext_azurelargeinstance/aaz/latest/large_instance/_update.py
Outdated
Show resolved
Hide resolved
…ge_instance/_update.py
[Release] Update index.json for extension [ azurelargeinstance ] : https://dev.azure.com/azclitools/release/_build/results?buildId=169200&view=results |
* Adding 2024-04-10 api version * Added updates to history.rst and updated version in setup.py * Updated tests since previous resource was deleted * Updated recorded tests * Fixed parameter name * Fixing parameter names * Update src/azurelargeinstance/azext_azurelargeinstance/aaz/latest/large_instance/_update.py --------- Co-authored-by: Ashwin Jeyaseelan <ashwinjeyaseelan@ashwins-mbp4.mynetworksettings.com> Co-authored-by: Ashwin Jeyaseelan <ashwinjeyaseelan@Ashwins-MacBook-Pro4.local> Co-authored-by: kai ru <69238381+kairu-ms@users.noreply.github.com>
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 azdev
required)python scripts/ci/test_index.py -q
locally? (pip install wheel==0.30.0
required)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.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
.