Simplify Template Deployment with new Template Specs!
Вставка
- Опубліковано 5 лип 2024
- A walkthrough using the new Template Specs feature to greatly simplify deploying ARM templates to Azure.
GitHub repo at github.com/johnthebrit/AzureM...
00:00 Introduction
00:32 ARM template 101
02:52 Challenges for usage
03:50 Template spec introduction
07:05 Template spec basic demo
08:22 Portal template spec creation
09:50 PowerShell template spec creation
12:07 Deploying a template spec
15:20 Using parameters with template specs
17:08 Adding a new version of a template spec
19:30 Linked templates
23:40 Relative linked templates with template specs
27:13 Referencing template specs in ARM files
29:50 Close - Наука та технологія
Thanks John, this helped a bunch with understand how to integrate the parameters into the template file. I download a template for automation, added it to the library to only find that it adds the template only and not the prameters. I should have saved the prameters file off separately so i can resuse from the CLI. I couldn't see a way to import or use the prameters file within the GUI/portal. But of course I could edit the template and use the defaultValue, to add them.
John thank you, I have been using Azure for many years but sometime I find Microsoft documentation so confusing and I'm thankful for your UA-cam posts. This particular video helped me with using Linked Template Specs and linked templates. Thank you.
Glad it was helpful!
Yes, really interesting! I'd definitely have used it if was available when I designed our internal CD system. Thanks for the video, John.
Glad it was helpful!
Thanks John, really helpful! I've been looking at this to assist with AMBA rollout!
Great to hear!
Great video and a really useful feature. Thanks John.
Very welcome.
This is GREAT! I'm just diving into the world of ARM
Good timing :-)
This is great and really making life easier, thank you John.
My pleasure.
Great content! I'm already having ideas where this could be useful in my current environment.
Perfect!
Amazing, I thought I knew everything, thanks a lot for the information and video.
My pleasure!
very nice, thank you
Really interesting, Thanks John. Can definitely see the use case here! On a side note you mentioned Bicep and in another video you alluded to doing a deep dive on Bicep, an idea when that might be? I did initially have a play with it when it was first announced but I am really eager be able to run with this... :)
once 0.3 hits i'll create a video.
Thanks John as always great video! How would you work with separate parameter files with this method? For instance we have a network template that has a different parameter template for each subscription how would this work with Template specs?
remember parameter files change by environment/deployment so would be different for each group so they may just keep those in a repo. its the template you don't want to change hence that makes sense in a spec.
Love it
Great video as always John! It's great to see the template specs making ARM templates more usable! One question: Do you recommend these over blueprints, or when would you suggest one over the other? Thanks!
so today blueprints have the deny capability that I can't do with ARM templates so you may still need blueprints for that locking via deny. policy, RBAC etc I can all do with templates.
@@NTFAQGuy Yeah, I was actually going to ask about that deny RBAC option too (do you have a video about that yet that I may have missed? If not, I'd love to see maybe one of your smaller 360 ones, since it's just a small piece of RBAC). So, aside from that deny piece though, how do you usually decide when you want to make it into a blueprint vs. a spec? Are the specs going to gradually replace blueprints? Thanks again! :-)
there is no way to do deny today outside blueprint and app features. there are other things coming and when available I'll create a video on them :-)
Personal opinion: I see blueprints are more geared towards a landing zone instantiation and management (multi resource groups, policies, RBAC), while specs are geared towards a single resource group deployment (can be driven through code to do something similar to blueprints). But both do have some overlapping features
Thanks John. Do you know if we can run these templates under a service principle, or do they have to run as the user who executes it?
It can run like any other template. If you have cicd as service principal will run as that fine.
@@NTFAQGuy Cheers John
Awesome work John! really what I was wondering today that is there a way to use something else other than storage account or git to store and I came across your video. I am going to work on converting our Linked Templates with Template Specs. Since these are all ARM based would you recommend them instead of Terraform (as if customer was using Terraform then we wld not be able to use Template Specs)?
I wouldn’t move from terraform if using already. This is a great feature for arm templates.
@@NTFAQGuy Thank you sir! You are awesome as always! Now since ARM is native to Azure and if a customer is only Azure focussed (no other cloud provider) would you recommend staying with ARM instead of moving to Terraform (Just because Terraform is easy to use). And from what I gathered Terraform uses ARM under the hood anyways. (Side note:- You have most respect from me as you completed Iron Man, I could figure that from your T-shirts! This is Big thing)
@@ketanshah9082 anything talking to azure uses ARM API but terraform does not compile to an ARM template. If you are Azure only no harm staying with ARM templates and bicep makes them easier to code.
@@NTFAQGuy Thank you so much John! Appreciate it and one more thing your teaching is super awesome THE BEST!
Can you do a video on solarwinds breach?
i'm not an intrusion specialist so not the right person really.