I have step by step and successful . in 7:32, Azure resource group deployment , the name have been change to ARM Template deployment . really thank you very much.
Kamil, Deployment of storage got successful from Dev to UAT. But the files contained within storage is not deployed into UAT. Am I doing something wrong or is it an expected behavior. Please guide me.
No, it's absolutely fine. ARM Template deploys infrastructure for you, not data or files. If you want to deploy some static files against environments you must use an additional task to do so. You may store the files in your code repository and deploy after infra deployment or in the separate pipeline.
Life saver. You are awesome,sir. Keep sharing. Sir, I have one question let say if resource group contains multiple services like ADF, Databrick, database etc. Do we have to implement each component separately for CI-CD or we can do the same in one go for all the services with single exported file like you have explained above.
Thank you, Santosh. Answering your question: Having everything in one big ARM template is possible but not recommended though. Firstly, due to limitations of ARM template: docs.microsoft.com/en-us/azure/azure-resource-manager/templates/template-best-practices Using several templates (separate per each service) will give you many benefits like maintainability, share, modularity, testability. Distinct templates also help you deploy infrastructure together or individually. Furthermore, each small template can be re-used easily in various projects.
This is one of many reasons why I do not recommend ADF deployment from ARM template / adf_publish branch. What I highly recommend is to deploy all ADF artifacts from code using RestAPI. You can create your own framework/script or use an existing PowerShell module. A month ago I created a PowerShell module which does ALL the things when it comes to deployment: github.com/SQLPlayer/azure.datafactory.tools. Furthermore, yesterday, I published Azure DevOps custom task for publishing ADF. The task uses mention PS module behind the scenes, enabling you to publish your whole ADF with one task in Release Pipeline. Check this out: Microsoft Marketplace: marketplace.visualstudio.com/items?itemName=SQLPlayer.DataFactoryTools