-
Notifications
You must be signed in to change notification settings - Fork 66
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
Version 0.8.4 breaks existing IoT Edge deployment command #113
Comments
In order to resolve this issue ASAP, I just help created a PR to revert the changes: Azure/azure-cli-extensions#1025. Please help sign off the PR. |
@digimaun Please help fix this issue. |
@blackchoey , we'll release a new version that re-adds the deprecated parameter. We can't revert because 0.8.4 has new functionality.
BTW you can pin to a specific version of the extension using --source install method i.e. |
Ok version v0.8.5 was just merged to the extension index. This release only re-adds the deprecated param. |
@digimaun Thank you very much for the quick turnaround. Do you have a list of deprecated commands/parameters? I would like to update all the deprecated commands/parameters in our task. |
Fortunately there is not that many so far. Quick overview:
|
Our Azure Pipelines task for IoT Edge uses following command to create IoT Edge deployment
az iot edge deployment create --config-id xxx --hub-name xxx --content xxx --target-condition xxx --priority xxx --output none
. However, the latest release0.8.4
has a breaking change that changed--config-id
to--deployment-id
and we didn't get official announcement in advance.Since Azure CLI can only install the latest version of extensions, please change the version of IoT extension back to 0.8.3 in Azure CLI extension index to avoid breaking existing commands. And we and other users can have enough time to update existing commands which uses
--config-id
parameter.The text was updated successfully, but these errors were encountered: