-
Notifications
You must be signed in to change notification settings - Fork 1.5k
{CI} Fix command tree broken issue #6573
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
Conversation
️✔️Azure CLI Extensions Breaking Change Test
|
|
Hi @wangzelin007, |
|
Hi @wangzelin007, |
|
CI |
|
It's better to update it here
|
Juliehzl
left a comment
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.
we do not want to be a special case with such exclusion. Let's discuss for better solution next week.
This reverts commit 3df4a81.
This reverts commit 3df4a81.
* Revert "{CI} Update the --dependent-file parameter to be an optional argument to avoid introducing a breaking change. (#6521)"
This reverts commit b442cf0.
* Revert "{CI} Fix verify ref docs (#6507)"
This reverts commit f12d922.
* Revert "{CI} Fix command tree broken issue (#6573)"
This reverts commit 3df4a81.
* revert linter

When two extensions have the same command, the following error will be reported:
Exception: Key: show already exists in containerapp. 2 extensions cannot have the same command!Temporarily skip the containerapp-preview extension to aviod this error.
Which will cause the containerapp-preview extension to be unable to use the dynamic load function.
That is, when using the unique command of containerapp-preview, the extension cannot be automatically prompted to install.
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?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.