Note that CI will fail if this metadata does not match the contents of your published extension. azext_metadata.json (if it exists) under your extension.This metadata is garnered from the setup.py folder. metadata.json located in your unzipped extension artifact (.The metadata needed to be filled is a combination of the contents present in: This will gather the appropriate metadata and add an entry for your extension to the index. Run azdev extension update-index where URL is the fully-qualified URL to your published extension WHL. ![]() The azdev extension update-index command can be used to simplify the process of updating the index file. How to fill in the metadata for an index.json entry? Note: Hash should be in lowercase in index.json otherwise CI will fail. Get-FileHash path_to_whl.whl -Algorithm SHA256 If you use azdev extension update-index the command will calculate the SHA256 digest for you. FAQ How to generate sha256digest for an index.json entry? ![]() If you want to host the source code in your dedicated repo, you have to upload the WHL file and update the src/index.json manually.įor detail, please visit Publish section in Azure CLI Extension Authoring. ![]() The precondition is to put your code inside this repo and upgrade the version in the PR but not to modify src/index.json. Once your PR is merged into master branch, a new PR will be created to update src/index.json automatically. There is a pipeline to automatically build, upload and publish extension wheels.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |