[MUSIC]
>> Hi, in this video,
we are going to look at
the Template Validator tool which is one of
the tools among the many that are
hosted on GitHub for the Azure Stack set off tools.
You could get hold of this tool by going to HTTPS://
Github.com/Azure/AzureStack-Tools
Once you have downloaded this set of tools,
you would find one of
the tools under the set of tools is the Template Validator.
Now it comes with primarily three files.
One, the PowerShell script.
Second, the Azure Stack capabilities JSON file,
of this JSON file is nothing but a set of
services and VM sizes
that are available in your Azure Stack instance.
So let me point you to this file.
So if you notice,
it defines what are the various VM sizes that are available?
What are the VM extensions that are
available with the Azure Stack instance?
Now this is the file that you're
template is compared against to be able to tell
you if you have a VM size that is defined in
a template for example that's
outside of what is available in Azure stack,
it would flag that off.
Now the third file is the Readme file that you see there.
Now let's go ahead and put this into use.
Now I have a template that I
often use to be able to deploy
a two-tier application into public Azure.
Now let me show you the template real quick.
This is my template.
What it has is if you notice in terms of
resources it has a back-end SQL Server,
SQL DB within the SQL Server.
A front-end it has,
I create an absolute plan,
a web app, and a Web Deploy package.
Now I'm going to take this template and I would want to
reuse this with my Azure Stack instance.
Before doing that, I would first want to "Validate" this template
with the Template Validator tool that is made available to me.
To be able to see whether I could
use this template as is or what are the changes that
I need to make to be able to run this template and
deploy my resources within my Azure Stack instance.
A how do I run this tool? It's pretty simple.
I open "PowerShell," navigate to the location or to
the path where I have downloaded my Template Validator.
Now as the first step,
I'm going to define a template path variable and set
it to or point it to my template file,
which is my JSON file location.
Once that is done,
I'll simply click "Enter" and that's set for me.
Next, I have a variable
which defines my capabilities path file
which is again the JSON I showed you,
which has the various sizes, extensions etc.
I hit "Enter" and I set this.
Then the third and the final step that I'm going to run is this.
I'm going to test my Azure Resource Manager Template,
with the variables that I have defined.
I'm going to run it in "Verbose mode" so that it
could show the output onto the PowerShell screen itself.
Let's go ahead and do that.
That's it. My template is validated.
You see the output here.
So some of the things that you would see is not supported,
resource type, firewalls, rules is not supported, etc.
You don't have to look at this, what you could do,
is you could go back to the folder from where we ran the tool,
and you would notice that a report is generated for you.
Let me go ahead and open this report.
So this is my report.
It shows me the time,
date and time it ran.
It showed me how many of my templates paths.
In this case, I just ran it against one template.
Whatever, any exceptions, warnings, not supported, etc.
So this template came out as not supported,
and the reason for that is this under the detail spin.
If you notice, there are resource types, like for example,
SQL Servers that aren't yet
supported with this current release of Azure Stack to be able to
deploy using Azure ARM
templates with Visual Studio
and that's my this is not supported yet.
This is the extensive reported gives so that you
know what is the reason
if it's not supported or what are the exceptions,
what are the warnings that it would generate,
and what is what is the recommendation. Thank you for watching.
[MUSIC]