swagger-to-cli-automation-config

[qiaozha]

---

This checklist is used to make sure that common guidelines for a pull request are followed.

General Guidelines

• Have you run azdev style <YOUR_EXT> locally? (pip install azdev required)
• Have you run python scripts/ci/test_index.py -q locally?

For new extensions:

• My extension description/summary conforms to the Extension Summary Guidelines.

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.

[azuresdkci]

If this PR is for a new extension or change to an existing extension, use the following to try out the changes in this PR:

docker run -it microsoft/azure-cli:latest
export EXT=<NAME>
pip install --upgrade --target ~/.azure/cliextensions/$EXT "git+https://github.com/Azure/azure-cli-extensions.git@swagger-to-cli-automation#subdirectory=src/$EXT&egg=$EXT"

[yonzhan]

add to S168

[mmyyrroonn]

is it on purpose to remove output-folder?

[qiaozha]

yes. the latest @autorest/az package 1.3.2 use --azure-cli-extension-folder instead of --output-folder to specify the output location. @autorest/az will add the src/extension-name.
it also allows the --clear-output-folder except manual folder.
Futher info can found here.
https://github.com/Azure/autorest.az/blob/master/doc/faq.md#what-would-the-clear-output-folder-clear
But please don't merge it now. @tiramisuq still needs some change in the swagger pipeline to make the automation work.

[mmyyrroonn]

sure. Ping me when this PR is ready to merge.