Not exactly what I was looking for. However, it did help me a great deal. I am trying to replicate pipeline created by data engineer couple of years ago (they have left since then). In place of arm template deployment, they are using Copy Files to X location and then Publish Artifact. Not sure, how that works but your video helped me understood other things around that.
Не ожидал, что Нагиев умеет так классно в Биг-дату!!! 😎👏🌟👍👏🌟👍Контент - АГОНЬ!!! 🔥🔥🔥🔥🔥🔥 Благодарю за труд!!! Заходит в кайф!!! 👍👍👍👍👍👍 Не останавливайся!!! 🚀🚀🚀🚀🚀🚀
Great job! I was able to follow your simple steps to revisit a problem I was experiencing with adf_publish. I did not have GIT configuration Publish branch set up correctly. It was pointing to the collaboration branch.
Does your release do anything that isn’t already done by your build pipeline? It seems like you are just deploying the ARM template to QA twice: once from build pipeline and again from release.
Exactly. But I don’t think he is deploying twice. The second release pipeline would be just earmarking the build so that we can revert back the build if needed using release number. That’s my guess but were you able to figure this out?
Hi, sir. Thank you very much for this! It saved me a lot of time. I have one little question: what if the data factorys are in two different resource groups? Thank you very much again.
@@hma262 Yeah good call. I should have finished the video before commenting lol. He specifically says the Resource group you pick when creating the pipeline is where you want it to be deployed too (for anyone else following along).
Is it possible to change pipeline parameters or activity settings when moving from dev to QA? In some activities like web activity URL might be different for environment, how can we handle that?
totally agreed, I recorded this video because I got so frustrated with it one day that I could only imagine how other people felt so I wanted to do something to help out.
This is not really the way to do it. You don’t want a deploy per environment in a classic pipeline. Using pipeline as code and then having the ARM template defined with variables and have arm template variable files per environment. You can then generate they variable files on the fly by just generating them from the template.
Short and straight to the point - This is exactly what I needed! Thank you!
Not exactly what I was looking for. However, it did help me a great deal. I am trying to replicate pipeline created by data engineer couple of years ago (they have left since then). In place of arm template deployment, they are using Copy Files to X location and then Publish Artifact. Not sure, how that works but your video helped me understood other things around that.
Не ожидал, что Нагиев умеет так классно в Биг-дату!!! 😎👏🌟👍👏🌟👍Контент - АГОНЬ!!! 🔥🔥🔥🔥🔥🔥 Благодарю за труд!!! Заходит в кайф!!! 👍👍👍👍👍👍 Не останавливайся!!! 🚀🚀🚀🚀🚀🚀
It's very informative.... Please add more videos on ADF real time scenarios.
Great job! I was able to follow your simple steps to revisit a problem I was experiencing with adf_publish. I did not have GIT configuration Publish branch set up correctly. It was pointing to the collaboration branch.
Very concise and to the point ...good job ...Thanks!!!
Great content, thanks. Just wondering, you don't need a separate repo for QA, right? Like the QA ADF won't be connected to any repos?
Dude.... it's perfect! Thank you very much!
u have not shown release pipeline task
Very fluid and extremely helpful demo, thanks a lot🙏🏾
Extremely helpful video. Thanks 🙏
Thank you for the video! Very nice tutorial!
Your Video was very helpfull for a deploy I`m doing, thanks a lot Sr
Does your release do anything that isn’t already done by your build pipeline? It seems like you are just deploying the ARM template to QA twice: once from build pipeline and again from release.
Great catch, just realized that he did not go to the details of what’s in the release pipeline at all🤔
Exactly. But I don’t think he is deploying twice. The second release pipeline would be just earmarking the build so that we can revert back the build if needed using release number. That’s my guess but were you able to figure this out?
Can you create video for deployment using YAML file Thanks
Great Job bro..very useful. Thanks for posting it!
Do you need an extra step to publish the pipelines you deployed in QA? or how do you publish in the QA data factory?
Hi, sir. Thank you very much for this! It saved me a lot of time. I have one little question: what if the data factorys are in two different resource groups? Thank you very much again.
I have the same question. All of my environments are in different resource groups.
@@GuyBehindTheScreen1 it's possible. I did it using "ARM template deployment" agent and specifying the target group resource
@@hma262 Yeah good call. I should have finished the video before commenting lol. He specifically says the Resource group you pick when creating the pipeline is where you want it to be deployed too (for anyone else following along).
Nice video bro, greetings from chile.
If I created my project in QA at first, it works the same to copy from QA to DEV?
Is it possible to change pipeline parameters or activity settings when moving from dev to QA?
In some activities like web activity URL might be different for environment, how can we handle that?
How did you get the keyvault parameter to show up in your parameter files
thanks a lot for This tuto,
👏helpful for me
when using the template currently, there is no elipsis to click to show the files. any ideas? thank you
sorry, this is video was recorded a while ago, and some options might have changed.. we will look into updating it soon
Great video! Thanks!
Good tutorial. Thanks a lot
Great Content!
Awesome!
Thanks !! You are an angel 😇
Great video Thanks
Very helpful thank you 😊
Hi....please show me Qa adf code..once deploy....in qa it should be run
Thanks for your helpful vid but I got to admit MS as usual overcomplicate everything its so long winded. Deployment should be much easier than this
totally agreed, I recorded this video because I got so frustrated with it one day that I could only imagine how other people felt so I wanted to do something to help out.
This is not really the way to do it.
You don’t want a deploy per environment in a classic pipeline. Using pipeline as code and then having the ARM template defined with variables and have arm template variable files per environment. You can then generate they variable files on the fly by just generating them from the template.
omg I managed to delete several Azure resources with this stupid ARM template. THIS THING IS DANGEROUS!
ouch