Hi Travis, I'd recommend you use only commands whenever is possible and forget about tasks. In this scenario, for example, you will probably face a problem if you need to deploy a hub-spoke in different subs because you can't reference it properly. Nice video, and keep it up.
I hope this could have been a bit simpler, like creating only a single resource (e.g. Storage Account) just to sideline that bit of "complexity" when deploying bastion. But still a great video overall
How do you handle the scenario where you want to create a pull request into the master branch and deploy the resources without cleaning them up? For example, I am happy with my deployment and I want to deploy it into production?
Incredibly useful, thank you
Thank you Travis. It is a great video
Hi Travis, I'd recommend you use only commands whenever is possible and forget about tasks. In this scenario, for example, you will probably face a problem if you need to deploy a hub-spoke in different subs because you can't reference it properly. Nice video, and keep it up.
Thanks for the tip!
Where is the link of the series for creating bicep files?
Thanks. I have a doubt. Why you use pipelines instead of the delivery section to deploy resources.
How to target particular azure bicep module using azure devops pipeline
Thx! Great video :)
Thank you for the awesome video. When we deploy more resources together via bicep, which resource get to deploy first? does it have an order ?
I hope this could have been a bit simpler, like creating only a single resource (e.g. Storage Account) just to sideline that bit of "complexity" when deploying bastion.
But still a great video overall
How do you handle the scenario where you want to create a pull request into the master branch and deploy the resources without cleaning them up?
For example, I am happy with my deployment and I want to deploy it into production?
The Job called Clean Up Resources is just for testing purposes. You'd remove that Job so that the resources will remain