gem-hunter
Language: TypeScript
Automate your GitHub workflows using Azure CLI scripts
Warning
Starting with Azure CLI version 2.64.0, the Azure CLI docker image will be based on Azure Linux. The az commands are not affected by this change. To ensure the compatibility of your pipelines, please migrate Alpine-specific commands to Azure Linux commands in the scripts used in the azure/cli action.
For more information, see https://go.microsoft.com/fwlink/?linkid=2282203.
With Azure CLI GitHub Action, you can automate your workflow by executing Azure CLI commands to manage Azure resources inside of an Action.
The action executes the Azure CLI Bash script on a user defined Azure CLI version. If the user does not specify a version, the version of Azure CLI installed on the agent is used. If there is no version of Azure CLI found on the agent, the action falls back the version to latest.
Read more about various Azure CLI versions here.
azcliversion – Optional Example: 2.30.0, Default: set to az cli version of the agent.inlineScript – RequiredAzure CLI GitHub Action is supported for the Azure public cloud as well as Azure government clouds ('AzureUSGovernment' or 'AzureChinaCloud') and Azure Stack ('AzureStack') Hub. Before running this action, login to the respective Azure Cloud using Azure Login by setting appropriate value for the environment parameter.
The definition of this GitHub Action is in action.yml. The action status is determined by the exit code returned by the script rather than StandardError stream.
Note
Please note that the action executes Azure CLI script in a docker container. This means that the action is subjected to potential restrictions which arise from containerized execution. For example:
GITHUB_WORKSPACE directory in host is mapped to working directory inside container. So, if the action wants to create a file, which will be read by subsequent actions, it should do so within current working directory tree.Warning
By default, the output of Azure CLI commands is printed to the stdout stream. Without redirecting the stdout stream, contents in it will be stored in the build log of the action. Configure Azure CLI to not show output in the console screen or print in the log by setting the environment variable AZURE_CORE_OUTPUT to none. If you need the output of a specific command, override the default setting using the argument --output with your format of choice. For more information on output options with the Azure CLI, see Format output.
azcliversion or azcliversion >= 2.30.0 for all the workflows. Authentication via connection strings or keys do not require this step.# File: .github/workflows/workflow.yml on: [push] name: AzureCLISample jobs: build-and-deploy: runs-on: ubuntu-latest steps: - name: Azure Login uses: azure/login@v2 with: creds: ${{ secrets.AZURE_CREDENTIALS }} - name: Azure CLI script uses: azure/cli@v2 with: azcliversion: latest inlineScript: | az account show az storage -h
# File: .github/workflows/workflowForFile.yml on: [push] name: AzureCLISampleForFile jobs: build-and-deploy: runs-on: ubuntu-latest steps: - name: Azure Login uses: azure/login@v2 with: creds: ${{ secrets.AZURE_CREDENTIALS }} - name: Checkout uses: actions/checkout@v4 - name: Azure CLI script file uses: azure/cli@v2 with: azcliversion: 2.30.0 inlineScript: | chmod +x $GITHUB_WORKSPACE/sampleScript.sh $GITHUB_WORKSPACE/sampleScript.sh
GITHUB_WORKSPACE is the environment variable provided by GitHub which represents the root of your repository.If you encounter an issue related to the Azure CLI commands executed in your script, you can file an issue directly on the Azure CLI repository.
This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.opensource.microsoft.com.
When you submit a pull request, a CLA bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., status check, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.
This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.