Merge pull request #239486 from alexlzx/alex-2305

updates articles for Azure Stream Analtics

Author: ttorble

articles/stream-analytics/TOC.yml

@@ -350,11 +350,31 @@
       href: set-up-cicd-pipeline.md
     - name: Set up a pipeline using GitHub Actions
       href: cicd-github-actions.md
+    - name: Deploy jobs with Bicep
+      href: cicd-deploy-with-bicep.md
     - name: Configure autoscale settings
       href: cicd-autoscale.md
+  - name: Visual Studio Code
+    items:
+    - name: Export and manage jobs
+      href: visual-studio-code-explore-jobs.md
+    - name: Test locally with live data
+      href: visual-studio-code-local-run-live-input.md
+    - name: Complete code with IntelliSense
+      href: vs-code-intellisense.md
+    - name: Run jobs locally with VS Code
+      href: visual-studio-code-local-run-all.md
+    - name: Test locally with sample data
+      href: visual-studio-code-local-run.md
+    - name: Debug queries using job diagram
+      href: debug-locally-using-job-diagram-vs-code.md
+    - name: Create and debug .NET custom deserializer
+      href: visual-studio-code-custom-deserializer.md
+    - name: JobConfig.json fields
+      href: job-config-json.md
   - name: Visual Studio
     items:
-    - name: Migrate Stream Analytics projects to VS Code
+    - name: Migrate to VS Code
       href: migrate-to-vscode.md
     - name: Quickstart
       href: stream-analytics-quick-create-vs.md
@@ -376,24 +396,6 @@
       href: stream-analytics-edge-csharp-udf.md
     - name: Set up CI/CD pipeline
       href: stream-analytics-tools-for-visual-studio-cicd.md
-  - name: Visual Studio Code
-    items:
-    - name: Complete code with IntelliSense
-      href: vs-code-intellisense.md
-    - name: Run jobs locally with VS Code
-      href: visual-studio-code-local-run-all.md
-    - name: Test locally with sample data
-      href: visual-studio-code-local-run.md
-    - name: Test locally with live data
-      href: visual-studio-code-local-run-live-input.md
-    - name: Debug queries using job diagram
-      href: debug-locally-using-job-diagram-vs-code.md
-    - name: Explore jobs
-      href: visual-studio-code-explore-jobs.md
-    - name: Create and debug .NET custom deserializer
-      href: visual-studio-code-custom-deserializer.md
-    - name: JobConfig.json fields
-      href: job-config-json.md
   - name: Troubleshoot
     items:
     - name: Input

articles/stream-analytics/cicd-deploy-with-bicep.md

@@ -0,0 +1,54 @@
+---
+title: Deploy Azure Stream Analytics jobs using Bicep files
+description: This article shows you how to generate and deploy Azure Stream Analytics jobs using Bicep files. 
+ms.service: stream-analytics
+author: alexlzx
+ms.author: zhenxilin
+ms.date: 05/24/2023
+ms.topic: how-to
+---
+
+# Deploy Stream Analytics jobs with Bicep files
+
+The Azure Stream Analytics (ASA) CI/CD npm package allows you to build, test, and deploy your Stream Analytics projects in your CI/CD pipeline using Bicep files. This article walks you through how to generate bicep files and deploy your ASA jobs. 
+
+Follow this [guide](quick-create-visual-studio-code.md) to create a new Stream Analytics project using Visual Studio Code or export an existing one from the Azure portal.
+
+## Installation
+```powershell
+npm install -g azure-streamanalytics-cicd
+```
+
+## Build project with Bicep
+```powershell
+# Generate Bicep template
+azure-streamanalytics-cicd build --v2 --project <projectFullPath> [--outputPath <outputPath>] --type Bicep
+
+# Example: 
+azure-streamanalytics-cicd build --v2 --project ./asaproj.json --outputPath ./Deploy --type Bicep
+```
+
+The **build** command does a keyword syntax check and generates Bicep files. If the project is built successfully, you see two files created under the output folder:
+* **Bicep template file**: [ProjectName].JobTemplate.bicep
+* **Bicep parameter file**: [ProjectName].JobTemplate.bicep.parameters.json
+
+The default values for **parameters.json** file come from your project settings. If you want to deploy to another environment, replace the values accordingly.
+
+The default values for all credentials are null. You're required to set the values before you deploy to Azure.
+
+## Deploy to Azure
+
+```powershell
+az login
+
+az account set --subscription "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"
+
+az deployment group create --name demodeployment --resource-group {resource-group-name} --template-file .\DeployV2\{project-name}.JobTemplate.bicep --parameters .\DeployV2\{project-name}.JobTemplate.bicep.parameters.json
+```
+
+## Next steps
+
+* [Azure Stream Analytics CI/CD tool](cicd-overview.md)
+* [Automate builds, tests, and deployments of an Azure Stream Analytics job](cicd-tools.md)
+* [Set up CI/CD pipeline for Stream Analytics job using Azure Pipelines](set-up-cicd-pipeline.md)
+

articles/stream-analytics/cicd-overview.md

@@ -1,29 +1,25 @@
 ---
-title: Continuous integration and deployment for Azure Stream Analytics 
-description: This article gives an overview of a continuous integration and deployment (CI/CD) pipeline for Azure Stream Analytics.
+title: Continuous integration and continuous deployment of Azure Stream Analytics jobs
+description: This article gives an overview of setting up a continuous integration and deployment (CI/CD) pipeline for Azure Stream Analytics jobs.
 services: stream-analytics
 author: alexlzx
 ms.author: zhenxilin
 ms.service: stream-analytics
 ms.topic: how-to
-ms.date: 12/27/2022
+ms.date: 05/24/2023
 ---
 
-# Continuous integration and deployment (CI/CD) for Azure Stream Analytics
+# Continuous integration and continuous deployment (CI/CD) of Stream Analytics jobs
 
-You can build and deploy your Azure Stream Analytics (ASA) job continuously using a source control integration. Source control integration creates a workflow in which updating code would trigger a resource deployment to Azure. This article outlines the basic steps for creating a continuous integration and continuous delivery (CI/CD) pipeline.
-
-If you're new to Azure Stream Analytics, get started with the [Azure Stream Analytics quickstart](stream-analytics-quick-create-portal.md).
+You can build, test and deploy your Azure Stream Analytics (ASA) job using a source control integration. Source control integration creates a workflow in which updating code would trigger a resource deployment to Azure. This article outlines the basic steps for creating a continuous integration and continuous delivery (CI/CD) pipeline.
 
 ## Create a CI/CD pipeline
 
 Follow the steps to create a CI/CD pipeline for your Stream Analytics project: 
 
-1. Create a Stream Analytics project using VSCode.
-   
-    You can either create a new project or export an existing job to your computer using the ASA Tools extension for Visual Studio Code. Check out these two docs for more information:
-    * [Quickstart: Create a Stream Analytics job using VSCode](./quick-create-visual-studio-code.md) 
-    * [Export an existing job](visual-studio-code-explore-jobs.md#export-a-job-to-a-local-project)
+1. Create a Stream Analytics project using VS Code. You can either create a new project or export an existing job to your local machine using the ASA Tools extension for Visual Studio Code.
+    * [Quickstart: Create a Stream Analytics job using VS Code](./quick-create-visual-studio-code.md) 
+    * [Export an existing job](visual-studio-code-explore-jobs.md)
 
 2. Commit your Stream Analytics project to your source control system, like a Git repository.