azure-cli 2.0.21

[derekbekoe]

• Have you followed the guidelines for contributing?
• Have you checked that there aren't other open pull requests for the same formula update/change?
• Have you built your formula locally with brew install --build-from-source <formula>, where <formula> is the name of the formula you're submitting?
• Does your build pass brew audit --strict <formula> (after doing brew install <formula>)?

---

[ilovezfs]

decommissioned?

[derekbekoe]

The previous files will still be there. We will not remove them.
From now on though, we release based of a specific git tag so now we can just point to the github release archive. It seems this is more standard across package managers to just point to the GitHub archive if it's available.

(Previously, the .tar.gz was custom so we had to create it and host it ourselves)

[ilovezfs]

@derekbekoe you may still want to upload separate release artifacts to GitHub, even if you're just downloading the source archive tarball and reuploading it, to avoid getting caught up in this sort of situation #18044.

[derekbekoe]

Ah okay.
I changed the URL to https://azurecliprod.blob.core.windows.net/releases/azure-cli-2.0.21.tar.gz.
Does that work?

[ilovezfs]

Yup, that will be safer.

[derekbekoe]

Added to commit to fix CI.
Please merge when ready if it looks good to you.

[ilovezfs]

Thanks for the upgrade @derekbekoe! ❇️