Azure recently updated their signing key which broke the installation of Azure CLI 2. This change updates how we install the Azure CLI 2 using their latest signing key.
Where should the reviewer start?
The changes in utilities.sh
How can this be manually tested? (brief repro steps and corpnet-URL with change)
source utilities.sh
install-azure-cli-2
Azure CLI 2 should be installed successfully.
What are the relevant TFS items? (list id numbers)
TFS#153046,
Definition of done:
[x] Title of the pull request is clear and informative
[x] Add pull request hyperlink to relevant TFS items
[ ] For large or complex change: schedule an in-person review session
[ ] This change has appropriate test coverage
[ ] Get at least two approvals
Reminders DURING merge
If you're merging from a short-term (feature) branch into a long-term branch (like dev, release, or master) then "Squash and merge" to keep our history clean.
If merging from two longterm branches (like cherry picks from upstream, dev to release, etc) then "Create merge commit" to preserve individual commits.
eltoncarr
commented
6 years ago
What does this PR do? Please provide some context
Azure recently updated their signing key which broke the installation of Azure CLI 2. This change updates how we install the Azure CLI 2 using their latest signing key.
Where should the reviewer start?
The changes in utilities.sh
How can this be manually tested? (brief repro steps and corpnet-URL with change)
Azure CLI 2 should be installed successfully.
What are the relevant TFS items? (list id numbers)
TFS#153046,
Definition of done:
Reminders DURING merge