Thank you Matt for this excellent content. I especially appreciate that you explain "small" nuances, such as @11:40 where you explain the difference between "requiredonly" and "all" parameters, where you even explain (just with a short sentence) what "requiredonly" parameters mean (parameters without default values). These little things help me make sure I understand what it means to have requiredonly and all parameters. Keep up the good work.
Hey Patrick. Thanks for the comment and the feedback. I really appreciate you took the time to let me know - as a content creator that really helps a lot! Glad the video was useful for you 🙂
Thank you Matt for this content. I purchased your "Zero to Hero" course. I noticed that there are few videos in production. Are you planning to finished them any time soon?
Thanks for the support! Yes, absolutely aiming to keep the content for the course rolling out. Unfortunately the last 6 months threw a few hurdles my way and cause a delay in production. Planning is well underway for the next section!
Hi! In the json format I could do something like "${VAR_X}" in the json dile and later when i did 'azd up' it would prompt me asking for a value for var_x,im not finding how to so this in the new bicepparam,do you know?
Interesting. I’m not 100% following sorry, can you provide some more info? Alternatively, logging an issue on the Bicep GitHub might be the go, you can easily attach screenshots / output / examples, and there are people much more clever than I there 😀
bicep is an interesting abstraction. I dont like the lack of a state file or way to manage the infrastructure drift. It feel like terraform in its beginnings. thanks for the video
There is no state management - Bicep can query the state directly from Azure. This removes problems with collaboration when multiple developers are accessing the state file ala Terraform. There are therefore no issues with keeping the state file secure, or refreshing the state either!
OMG I can't belive it, no more Json
Thanks for your video!
You’re most welcome! And yep, good times with less JSON 😁
Thank you Matt for this excellent content.
I especially appreciate that you explain "small" nuances, such as @11:40 where you explain the difference between "requiredonly" and "all" parameters, where you even explain (just with a short sentence) what "requiredonly" parameters mean (parameters without default values). These little things help me make sure I understand what it means to have requiredonly and all parameters.
Keep up the good work.
Hey Patrick.
Thanks for the comment and the feedback. I really appreciate you took the time to let me know - as a content creator that really helps a lot! Glad the video was useful for you 🙂
@Matt Allford Nice video...
Thank you for watching!
Thank you Matt for this content.
I purchased your "Zero to Hero" course. I noticed that there are few videos in production. Are you planning to finished them any time soon?
Thanks for the support!
Yes, absolutely aiming to keep the content for the course rolling out. Unfortunately the last 6 months threw a few hurdles my way and cause a delay in production. Planning is well underway for the next section!
Hi! In the json format I could do something like "${VAR_X}" in the json dile and later when i did 'azd up' it would prompt me asking for a value for var_x,im not finding how to so this in the new bicepparam,do you know?
Interesting. I’m not 100% following sorry, can you provide some more info? Alternatively, logging an issue on the Bicep GitHub might be the go, you can easily attach screenshots / output / examples, and there are people much more clever than I there 😀
Can you make video on multi-stage container apps build & deployment CI/CD azure pipeline
Unfortunately I don’t really take requests on the content that I choose to produce here on the channel
Hi, can you video on disater recovery using azure bicep
Hey Satish, I don’t have anything planned on configuring the Azure DR services using Bicep at the moment.
bicep is an interesting abstraction. I dont like the lack of a state file or way to manage the infrastructure drift. It feel like terraform in its beginnings. thanks for the video
No worries at all, thanks for watching!
There is no state management - Bicep can query the state directly from Azure. This removes problems with collaboration when multiple developers are accessing the state file ala Terraform. There are therefore no issues with keeping the state file secure, or refreshing the state either!