Please align azure/login@v1 and azure/CLI@v1. It's really strange and not user friendly.
Given workflow where I first use azure/CLI@v1 to show current az version and then use azure/login@v1 it behaves quite weird.
az version actually shows latest version because this action actually pulls and runs microsoft docker image with azure cli,
but then the azure/login@v1 action fails because this one relies on az command being installed on self-hosted github runner.
- name: show az version
uses: azure/CLI@v1
with:
inlineScript: |
az version
- uses: azure/login@v1
with:
creds: ${{ secrets.SECRET }}
In my case the azure/login@v1 will fail on az command not being available because my runners are quite clean and az is not installed.
What is the reason to forcing users to both manage az on the hosts and also require having docker installed and pull docker images for actually performing any az actions?
I believe azure/login and azure/cli should use consistent approach in this case.
Please align
azure/login@v1andazure/CLI@v1. It's really strange and not user friendly.Given workflow where I first use
azure/CLI@v1to show current az version and then useazure/login@v1it behaves quite weird.az versionactually shows latest version because this action actually pulls and runs microsoft docker image with azure cli,but then the
azure/login@v1action fails because this one relies onazcommand being installed on self-hosted github runner.In my case the
azure/login@v1will fail onazcommand not being available because my runners are quite clean andazis not installed.What is the reason to forcing users to both manage
azon the hosts and also require having docker installed and pull docker images for actually performing any az actions?I believe
azure/loginandazure/clishould use consistent approach in this case.