-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
2024-01-01-preview #7392
2024-01-01-preview #7392
Conversation
❌Azure CLI Extensions Breaking Change Test
|
Hi @jamesfan1, |
Thank you for your contribution! We will review the pull request and get back to you soon. |
|
|
||
capacity = cls._args_schema.scaling_properties.profiles.Element.capacity | ||
capacity.max = AAZIntArg( | ||
options=["max"], |
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.
I am not sure how this looks like on Azure CLI but "min" and "max" are not good names as they don't tell the user much about what the min and max are about or applied to.
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.
--scaling-properties profiles=[{name:default,capacity:{min:10,max:30}}]
perhaps if we add this sample in the help command it should explain it?
@@ -143,6 +148,13 @@ def _build_arguments_schema(cls, *args, **kwargs): | |||
help={"short-summary": "Optional: Preferred communication email", "long-summary": "Usage --user-profile [email protected]"}, | |||
) | |||
|
|||
auto_upgrade_profile = cls._args_schema.auto_upgrade_profile | |||
auto_upgrade_profile.upgrade_channel = AAZStrArg( |
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.
is there a way to add some "help" around valid values? If so, can you please add preview
and stable
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.
fixed
tests are passing locally, not sure why it doesnt pass in the pipeline. All new command tested manually and succeeding |
Please fix CI issues |
@jamesfan1 there is a breaking change in this pr which deleted a parameter. If it's unintentional, please fix it, if it is intented, that's ok. Another problem is the version number, the last released version is For version details, please refer to our doc here |
src/nginx/HISTORY.rst
Outdated
@@ -3,6 +3,10 @@ | |||
Release History | |||
=============== | |||
|
|||
1.0.0b1 |
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.
please correct version number
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.
fixed, thank you
I am unsure what is wrong for it is passing locally, and generated a recording file however, on ci it's failing with ERROR cli.azure.cli.core.azclierror:azlogging.py:212 Can't overwrite existing cassette ('/mnt/vss/_work/1/s/src/nginx/azext_nginx/tests/latest/recordings/test_deployment_cert_config.yaml') in your current record mode ('once'). on this line, but this line runs fine locally have you seen such error? |
@@ -1,3 +1,3 @@ | |||
{ | |||
"azext.minCliCoreVersion": "2.55.0" | |||
"azext.minCliCoreVersion": "2.58.0" |
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.
Please set azext.isPreview
to true as you will release it as preview.
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
.