-
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
Build extension command tree #2078
Build extension command tree #2078
Conversation
Who's going to need this? |
I think the naming may cause confusion with the existing command index (Azure/azure-cli#13294). |
How about the name command tree as it mimics a prefix tree? |
PR:Azure/azure-cli#14478 needs to search command in a json file for all extension commands and the json file is built in this PR. |
Trie tree solution is good and the performance is fast. |
…xtension_cmd_index
…cli-extensions into extension_cmd_index
Add scripts to build a command tree json for all extensions and upload to a storage account.
These scripts will be used in the release sync pipeline of extensions. Test pipeline: https://dev.azure.com/azure-sdk/internal/_build?definitionId=1857&_a=summary
The json file will be used in Azure CLI, related PR: Azure/azure-cli#14478
An example of the built file:
This checklist is used to make sure that common guidelines for a pull request are followed.
General Guidelines
azdev style <YOUR_EXT>
locally? (pip install azdev
required)python scripts/ci/test_index.py -q
locally?For new extensions:
About Extension Publish
There is a pipeline to automatically build, upload and publish extension wheels.
Once your PR is merged into master branch, a new PR will be created to update
src/index.json
automatically.The precondition is to put your code inside this repo and upgrade the version in the PR but do not modify
src/index.json
.