Get the step-by-step tutorial and download the code from my site vtns.io/ytvazbicepazfunctutorial and check out my video showing how to implement CI/CD with GitHub Actions th-cam.com/video/36R1pzPuLvs/w-d-xo.html
Absolutely gold! Just what a Bicep newbee needs! I had gotten off to a good start but beyond getting things working, I pick up in this video some good direction for Doing It Right. I'll be sure to watch your other videos. Thanks a bunch!
Have you seen my other related video? I show exactly how I do this with GitHub Actions for a NodeJS based Azure Function App) - th-cam.com/video/36R1pzPuLvs/w-d-xo.html
Thanks Andrew. This an excellent way to educate and inform people trying to learn these skills. One of the very best Azure videos available anywhere. In fact, far superior to the videos I have seen from Microsoft. (They should compensate you for your high quality work, in my opinion). Thanks for creating this, please create more videos in this format. Thank you!
Great series. Well thought out and very clear. Do you cover running a bicep file multiple times and creating resources only if they don't already exist or changing them if they do exist?
Yup... Bicep (& ARM) templates are considered desired-state-configuration (DSC). In other words, if the resource you describe is NOT present, it's created. If it is present but doesn't match what's in the template, it's updated to reflect the changes. If it is present & identical to the template, it's ignored.
Thanks a lot for this video. Its really educational. I am very new to azure and cloud technology . I am facing an issue where my visual studio code terminal is running PowerShell as default. What are you using in your terminal. I have already installed Azure CLI and also have bicep extension in VS code application.
You're welcome! My preferred shell & prompt are Oh My ZSH & the Starship theme. For a terminal, I use Hyper (but Hyper isn't what's used in the VSCode integrated terminal... that's coming from OMZ & Starship).
Great video - very interesting to see BICEP. The keyboard tick/tack is kinda distracting, I couldn’t concentrate on your explanation ! (Can you mute/drop the keyboard noises…?)
Not sure if it would be popular enough to warrant its own video, but it would be great to see a follow-up video on how the process of deploying the Functions themselves works with Bicep. From the documentation, it looks like it's possible to deploy the individual Functions inside the Function App resource using Bicep, there's not an awful lot about how to actually do this and when it should be done this way instead of using a ZIP deployment.
This is helping me a ton, thanks! But I'm a little puzzled over the 'functionSlotConfig' resource you create at 00:19:50 which contains the names of the parameters that are slot specific. What would happen if you left this out and just had the two config resources you declare in the appsettings-config.bicep file? Aren't they enough to get your two sets of config parameters deployed? Thanks again!
Glad it's helping Adam! The reason why you want to specify the parameters to be slot specific is because if you don't, when you swap the slots, the setting won't "stick" to the slot. So, it's not as much of an issue with the setting of the values, rather it's an issue when you run a slot swap.
Hi Andrew, I have a question. I have a requirement that I have to create a webapp with different number of deployment slots(could be 2 or 3 or 4) and for all deployment slots including production slot I want to set different 'appsettings' and 'sticky appsettings' . According to the video I came to know that we can create production and staging slots only for Azure function apps and web apps. Can you explain me more on this ?
In your bicep file you define the "kind" as "functionapp", which deploys a linux function app. What is the value for "kind" if I want to deploy a Windows function app?
For the Function App, the 'kind' is still 'functionapp'... the platform is defined by the hosting plan. For Windows, you can use something like this: resource hostingPlan 'Microsoft.Web/serverfarms@2021-03-01' = { name: hostingPlanName location: location sku: { name: 'Y1' tier: 'Dynamic' } properties: {} }
![Warhammer 40k: Space Marine 2 | เพื่อจักรพรรดิ ! [ตอนเดียวจบ]](http://i.ytimg.com/vi/4M0ckYMA4-U/mqdefault.jpg)
![Megan Thee Stallion - Neva Play (feat. RM) [Official Video]](http://i.ytimg.com/vi/TpYTyAaTRts/mqdefault.jpg)
Get the step-by-step tutorial and download the code from my site vtns.io/ytvazbicepazfunctutorial and check out my video showing how to implement CI/CD with GitHub Actions th-cam.com/video/36R1pzPuLvs/w-d-xo.html
Absolutely gold! Just what a Bicep newbee needs! I had gotten off to a good start but beyond getting things working, I pick up in this video some good direction for Doing It Right. I'll be sure to watch your other videos. Thanks a bunch!
You’re welcome!
Great Stuff ! Looking forward to seeing how to deploy an actual app ( either NodeJS / C# / Python) to this App .
Have you seen my other related video? I show exactly how I do this with GitHub Actions for a NodeJS based Azure Function App) - th-cam.com/video/36R1pzPuLvs/w-d-xo.html
Thanks Andrew. This an excellent way to educate and inform people trying to learn these skills. One of the very best Azure videos available anywhere. In fact, far superior to the videos I have seen from Microsoft. (They should compensate you for your high quality work, in my opinion). Thanks for creating this, please create more videos in this format. Thank you!
Glad it was helpful!
awesome knowledge
Great series. Well thought out and very clear. Do you cover running a bicep file multiple times and creating resources only if they don't already exist or changing them if they do exist?
Yup... Bicep (& ARM) templates are considered desired-state-configuration (DSC). In other words, if the resource you describe is NOT present, it's created. If it is present but doesn't match what's in the template, it's updated to reflect the changes. If it is present & identical to the template, it's ignored.
Great video, but having a hard time concentrating on what you say over the generic keyboard typing sounds. :)
Thanks Kolbein... and noted. I've removed those from future videos.
Thanks a lot for this video. Its really educational. I am very new to azure and cloud technology . I am facing an issue where my visual studio code terminal is running PowerShell as default. What are you using in your terminal. I have already installed Azure CLI and also have bicep extension in VS code application.
You're welcome! My preferred shell & prompt are Oh My ZSH & the Starship theme. For a terminal, I use Hyper (but Hyper isn't what's used in the VSCode integrated terminal... that's coming from OMZ & Starship).
Great video - very interesting to see BICEP. The keyboard tick/tack is kinda distracting, I couldn’t concentrate on your explanation ! (Can you mute/drop the keyboard noises…?)
Thanks! I thought the keyboard would be a little fun, but a few people have said the same thing. Noted for future videos... thanks for the feedback!
Thanks - very useful video! The music at the start and the keyboard clicking is distracting, but otherwise perfect!
Not sure if it would be popular enough to warrant its own video, but it would be great to see a follow-up video on how the process of deploying the Functions themselves works with Bicep. From the documentation, it looks like it's possible to deploy the individual Functions inside the Function App resource using Bicep, there's not an awful lot about how to actually do this and when it should be done this way instead of using a ZIP deployment.
Did you by chance see the other video linked at the end of this one where I show all the workflows used to implement the CICD and deployment process?
@@Andrew_Connell Ah sorry, I missed that. I'll check that out!
This is helping me a ton, thanks! But I'm a little puzzled over the 'functionSlotConfig' resource you create at 00:19:50 which contains the names of the parameters that are slot specific. What would happen if you left this out and just had the two config resources you declare in the appsettings-config.bicep file? Aren't they enough to get your two sets of config parameters deployed? Thanks again!
Glad it's helping Adam! The reason why you want to specify the parameters to be slot specific is because if you don't, when you swap the slots, the setting won't "stick" to the slot. So, it's not as much of an issue with the setting of the values, rather it's an issue when you run a slot swap.
Hi Andrew, I have a question. I have a requirement that I have to create a webapp with different number of deployment slots(could be 2 or 3 or 4) and for all deployment slots including production slot I want to set different 'appsettings' and 'sticky appsettings' . According to the video I came to know that we can create production and staging slots only for Azure function apps and web apps. Can you explain me more on this ?
The production and staging slots are just two I use in this video. You can create more than that and then apply your workflow logic to each one.
In your bicep file you define the "kind" as "functionapp", which deploys a linux function app. What is the value for "kind" if I want to deploy a Windows function app?
For the Function App, the 'kind' is still 'functionapp'... the platform is defined by the hosting plan. For Windows, you can use something like this:
resource hostingPlan 'Microsoft.Web/serverfarms@2021-03-01' = {
name: hostingPlanName
location: location
sku: {
name: 'Y1'
tier: 'Dynamic'
}
properties: {}
}