1 hour 19 minutes
now what are linked? Adam Templates And why do you wanna use them? As we mentioned in the previous video,
you may wanna actually overcome some of the limitation of the arm templates. For that you may need to use linked on templates. But also, from organizational point of view, you may want to split the development of different arm templates between different teams or people.
Let's see how this work.
Imagine that you have already developed a template to deport your virtual network.
This is a stand alone template with these parameters,
variables and the resource. Is that the point?
Very simple. One.
If you would like to reuse this template in some other department
where you'll need to deform not only the virtual network but other resource is
you can link this template from a master template.
Is it the point? A virtual network resourced? Oh, you need to deploy or create the resource of type deployment.
So you see that the type is Microsoft or three sources large deployment, which is the resource identifier you name. This resource is nested veena template,
and you are a link to the template. Very often, those templates can be applauded in blob storage. So you can other Ling Tau, the blob location where the template is
as well as you can. Other link tow the para matters
file that you can be used with this template.
You can also add in line parameters if you instead, the perimeter slink, you are a parameters
put up out of here
However, linking templates is not the only option. You can also embed templates inside.
Here Is we embedded the creation of the storage account in the master template
again east it creating a storage account. We create a deployment.
And in the properties of the department, we have the actual template where the storage account is created.
This is the same structure that we used in our initial template when we started writing it.
They're certain benefits to linking to external templates than embedding them, but nevertheless you have both options.
Now let's talk about the deployment most that you can see we used in both linked and the embedded templates
actual resource manager Thio supports to deployment. Moz, the first is called complete more in a complete mother. Actual resource manager deletes all the resources that exist in the resource group,
but I don't specified in the template.
What that means is, if you have a resource group that he has, some resource is inside. Let's say you have already storage account or virtual machine there, and your deploy a new template in that resource group that here's a complete deployment month.
The existing storage account and virtual machine will be deleted before the new resource is sort of the point.
The other deployment modus called incremental moat in ink in incremental model resource manager leaves and changed. The resource is that exists in the resource group but aren't specified in the template,
taking our previous example where we hear the storage account in virtual machine in the resource group. If we do a incremental, more deployment in the template, then the new resources will be other. In addition to the existing ones in the resource group,
let's once again the review. What are the benefits of the linked templates?
The 1st 1 is, of course,
toe overcome the arm template limitations.
The two important limits that you need toe take care off us are the length of the template as well. What's the number of resource is you can deploy.
Let's say you wanted the boy 1000. Resource is you cannot do this with the single arm template because you're limited to only 803 sources.
This includes also resources that are created in cycles. Let's say you want to create virtual machines that are identical, but 10 or 20 of those.
If you have this cycle or loop in the arm template,
this count store towers the overall limit off 803 sources. In order to do this type of deployment, you need to use multiple templates that are linked to each other.
Another benefit of the link templates is that you can store the templates in central repositories and just link from new master templates. Toe does existing templates.
An example of such central depository can be a storage account.
Very similar benefit is when you want to go unattended deployments.
So if you're if you care for central depository for all the templates you can use, service is like azure automation or actual develops toe. Pull the templates from those central repositories and do that unattended or automated deployments.
Also, you can link to 1/3 party templates.
There many templates that you can find on get up and reusing your own templates.
So we saw in this video how we can use link templates to make our arm templates more flexible and reusable. Let's summarize the whole model.