Common design patterns with Azure Cosmos DB
Build with an Azure free account. Get USD200 credit for 30 days and 12 months of free services.
Start free todayContinuous integration and deployment using Azure Data Factory
Play Continuous integration and deployment using Azure Data Factory
Description
Gaurav Malhotra joins Scott Hanselman to discuss how you can follow industry-leading best practices to do continuous integration and deployment for your Extract Transform/Load (ETL) and Extract Load/Transform (ELT) workflows to multiple environments such as Dev, Test, Prod, and more.
For more information:
- Continuous integration and deployment using Data Factory (Azure blog)
- Continuous integration and deployment in Azure Data Factory (Docs)
- Create a free Azure account
Follow @SHanselman Follow @AzureFriday Follow @gauravmalhot12
Download
More episodes in this series
Deploy Bitnami Node.js HA Cluster with Azure Cosmos DB
Related episodes
How to prepare data using wrangling data flows in Azure Data Factory
How to monitor your Azure Data Factory pipelines visually using Gantt views
How to execute Azure Machine Learning service pipelines in Azure Data Factory
Create dependent pipelines in your Azure Data Factory
Build ETL pipelines collaboratively using Git integration in Azure Data Factory
Code-free modern data warehouse using Azure SQL DW and Data Factory
Rerun activities inside your Azure Data Factory pipelines
Quickly build data integration pipelines using templates in Azure Data Factory
Code-free data transformation at scale using Azure Data Factory
Monitor your Azure Data Factory pipelines proactively with alerts
The Discussion
-
Koos van Strien Great stuff! However, when I (or my CI process) exports an ARM template with an SSIS Integration Runtime, the "catalogServerEndpoint" as well as the "catalogAdminUserName" are not parameterized, which makes it hard to release this artifact on multiple environments continuously.
I could write a script to alter the JSON after publishing the ARM template, but IMHO that isn't the way to go :). Is there a way to get the endpoint & admin username parameterized by default as well?