Azure Stream Analytics Updating a Job using a GitHub Action to stop and start

Effortlessly deploy Azure Stream Analytics jobs with my TypeScript-based GitHub Action and Azure CLI.

Azure Stream Analytics Updating a Job using a GitHub Action to stop and start

Deploying Azure Stream Analytics Jobs with GitHub Actions: My Efficient Approach


Automating the deployment of Azure Stream Analytics (ASA) jobs has always been a priority for me to streamline workflows, reduce errors, and ensure consistency. For several years, I have been aware of the limitations and issues with the Terraform provider for AzureRM, as highlighted in the GitHub issue #19328. To address these challenges, I created the GitHub repository cicorias/action-asa-ts, which offers an efficient way to deploy ASA jobs using a TypeScript-based GitHub Action. In this post, I'll share my experience with the repository, its associated GitHub Action, and how it provides a reliable alternative to Terraform.

The Repository: cicorias/action-asa-ts

When I created the cicorias/action-asa-ts repository, my goal was to provide a solution that deploys Azure Stream Analytics jobs effortlessly. This action leverages the Azure CLI and a TypeScript script to handle the deployment process, ensuring that the jobs are deployed correctly and efficiently. The repository includes all the necessary code, documentation, and examples to get started quickly.

Key Features

  1. TypeScript-based Implementation: The action is written in TypeScript, providing type safety and modern JavaScript features, which I appreciate.
  2. Integration with Azure CLI: It utilizes the Azure CLI to interact with Azure services, ensuring a robust and reliable deployment process.
  3. Customizable Parameters: It allows you to specify various parameters such as the job name, resource group, and subscription ID.
  4. Error Handling: It implements comprehensive error handling to manage deployment failures gracefully, which is a huge plus for me.

The GitHub Action: Azure Stream Analytics Job Deployment

The Azure Stream Analytics Job Deployment GitHub Action from the repository can be integrated into any CI/CD pipeline to automate the deployment of ASA jobs. This action simplifies the process, making it accessible even for those who are not deeply familiar with Azure Stream Analytics or Azure CLI.


To use this GitHub Action, you can include it in your workflow file (.github/workflows/deploy.yml). Here’s an example of how I set it up:

name: Deploy ASA Job

      - main

    runs-on: ubuntu-latest

      - name: Checkout code
        uses: actions/checkout@v2

      - name: Set up Azure CLI
        uses: azure/login@v1
          creds: ${{ secrets.AZURE_CREDENTIALS }}

      - name: Deploy ASA Job
        uses: cicorias/action-asa-ts@v1
          jobName: 'my-asa-job'
          resourceGroup: 'my-resource-group'
          subscriptionId: ${{ secrets.AZURE_SUBSCRIPTION_ID }}

How the GitHub Action Helps

The GitHub Action provided in the cicorias/action-asa-ts repository addresses the challenges associated with the Terraform provider for AzureRM by offering an alternative deployment method. Instead of relying on Terraform, which may have unresolved issues, this action uses the Azure CLI, which is fully supported and frequently updated by Microsoft.

  • Reliability: Azure CLI commands are less prone to the issues reported in the Terraform provider, ensuring a more reliable deployment process.
  • Flexibility: The action can be easily integrated into existing GitHub workflows, providing flexibility in deployment pipelines.
  • Maintenance: The GitHub Action is maintained independently, allowing for quicker updates and fixes compared to waiting for updates in the Terraform provider.


As the author of the cicorias/action-asa-ts repository and its associated GitHub Action, I'm proud to offer a robust solution for deploying Azure Stream Analytics jobs. By leveraging TypeScript and the Azure CLI, this action provides a reliable and flexible alternative to Terraform, addressing common deployment issues. Integrating this action into your CI/CD pipeline can streamline your workflow, reduce errors, and enhance the overall efficiency of your deployments.

For more information and to get started, check out the repository and the GitHub Action on the GitHub Marketplace.

By adopting this approach, I’ve ensured my ASA job deployments are smooth and hassle-free, paving the way for more effective data stream processing in my Azure environment.