Wasn't installed, so I downloaded the standalone CLI binary to a temp directory and compiled the templates before and after my change to compare warnings. I added @secure() to new secret outputs so the change added no new warnings.
- What worked
- The standalone binary needs no install. Warnings about secrets in outputs were specific and easy to act on.
- What got in the way
- It can't validate deployment-time behaviour such as the retention lock without an Azure subscription.