Thanks for video, now I see better how different parts play together. What would be the way to automate this process of connecting and creating stuff between Azure DevOps AAD Subscription Storage, since it's kinda tedious/error-prone to do manually? I was thinking either some bash script or a terraform config without saving the state.
You read my mind. I am actually recording episodes this weekend on how to use the Azure DevOps terraform provider to automate this entire process! But shhh… don’t tell anybody. 🤣 look for it in upcoming multi-part episode series about how to “automate the automation”
By the way don’t miss my shout out to you in my provider release review v3.54.0! And thanks again for the ☕️! Appreciate the support! This is not a work project (just for fun) so I gotta pay my own Azure bills!!! 😀
Sir you are doing a Great job, i had a question is there a reason for having 2 subscription ids, can i have same subscription ids for both dev and prod
Thanks for the kind words!! Yes you can have the same subscription as both Dev and prod. That's another reason why I follow a strict naming convention to avoid naming conflicts within the same subscription or otherwise!
Yes some people prefer that approach. I don't like to tightly couple my backend details in actual code because I like the ability to potentially use different backends for the same code (Dev vs prod, etc)
Excellent Video 👍
Thank you very much!
Thanks for video, now I see better how different parts play together.
What would be the way to automate this process of connecting and creating stuff between Azure DevOps AAD Subscription Storage, since it's kinda tedious/error-prone to do manually? I was thinking either some bash script or a terraform config without saving the state.
You read my mind. I am actually recording episodes this weekend on how to use the Azure DevOps terraform provider to automate this entire process! But shhh… don’t tell anybody. 🤣 look for it in upcoming multi-part episode series about how to “automate the automation”
If someone were so inclined they might find something interesting on my GitHub feature branches…. 🤣
By the way don’t miss my shout out to you in my provider release review v3.54.0! And thanks again for the ☕️! Appreciate the support! This is not a work project (just for fun) so I gotta pay my own Azure bills!!! 😀
Thanks 😊
Sir you are doing a Great job, i had a question is there a reason for having 2 subscription ids, can i have same subscription ids for both dev and prod
Thanks for the kind words!! Yes you can have the same subscription as both Dev and prod. That's another reason why I follow a strict naming convention to avoid naming conflicts within the same subscription or otherwise!
I see that you have a backend script file for backend details is there any other ways we can maintain backends like in terraform file itself
Yes some people prefer that approach. I don't like to tightly couple my backend details in actual code because I like the ability to potentially use different backends for the same code (Dev vs prod, etc)
Its good. Is it possible to get the Lib var from KV ?
Oh yes. You can link an AzDO variable group to a keyvault and pull the credentials from there instead of storing them securely in AzDO.
Hello
Hello siva!