4.3 Deploying Azure Resources Using ARM and Azure CLI

00:00

Now, if you're on a mark or ah Lenox machine, you don't have power showing stop.

00:07

However, all the virtual machines that are created the national half the actual cli in start on them. Let's see how we can do the same things that we did with Power Shell with azure sea ally.

00:22

The first thing we need to do is to off course signing with Asher will do that by using a Z Logan

00:30

Seymour to the power show approach will get a browser window

00:42

and will be locked in automatically in the browser and window.

00:46

This will be closed in about 10 seconds.

00:49

Here we have a list off all our subscriptions that we have access to.

00:55

Next. Let's create a resource group using astral ***. CLI a C group

01:02

could be eight.

01:04

We need to put a name for the

01:07

resource group for call it cyber very

01:11

cli test our G

01:15

and of course, location which will be west. Us too.

01:22

So our resource group will be created. The next thing we can do is to start our deployment.

01:30

Toto, the department we need to use the ese group deployment,

01:36

create command

01:38

and we need to specify some information like the name of the deployment them played CLI deployment

01:49

the Resource Group

01:55

which will be the cyberbullying,

02:00

cli best research group.

02:05

And of course, the template file,

02:08

which will be our template. Jason,

02:15

Once we started the command,

02:17

the C l. I will ask us for the input will use the usual one cyber very for the app name and

02:28

uppercase death for our environment.

02:31

After a minute, the deployment will be complete and we can see the output from it.

02:38

Here is the output from our deployment using azure cli.

02:43

Now let's try to use the parameters files to deport the development in the production environment. However, one thing I will do here is East it creating a new resource group for the development environment. I will use the existing cyber very CLI Test resource group that we just used.

03:01

So we will do Pacey Group deployment

03:06

38

03:09

will specify name for the deployment arm Template

03:17

Seelye. Their deployment

03:22

We'll specify the resource group

03:27

which will be the same

03:30

cyber ready.

03:31

Cli

03:34

this G

03:38

then we'll specify more complete toe. Make sure whatever it is existing in this resource group is

03:47

deleted before we do our deployment.

03:51

Then we'll specify the template file,

03:55

which will be our template, Jason and the last thing will specify will be the parameters.

04:03

So they're fun. A few ways to specify the perimeters.

04:08

You can use a Jason four month. You can use key value pairs, or you can use the parameters found. The parameters file needs to be preceded by the art symbol.

04:20

So where's the party mentors there? Jason. File

04:25

for our deployment.

04:28

If you have three sources that are included in the template in your resource group and use complete malt, the department can be very fast. However, if you have different resource is that needs to be deleted before the deployment is done that the appointment can take a little bit longer.

04:45

Our deployment was very fast because we have the exactly same resource is in the resource group

04:50

else we have in the template.

04:53

Now let's go and do the production deployment So Social group create will create the

05:02

research group for the production.

05:04

We'll call it Cyber Larry

05:08

cli

05:10

out of G

05:12

you

05:14

West us too

05:17

and we'll do the way we use the same template. I'm template. However we different

05:25

parameters file to do our deployment and I will actually

05:30

modify the previous command.

05:32

So use the parameters brought J Song and we will use the

05:40

cyber body.

05:42

Brought our Jeanne

05:45

and we'll just name our deployment. I'm template cli probe deployment.

05:55

We'll start this deployment. It will take a minute or two to deport. The resource is and we'll get the output from it.

06:03

Our deployment is done. Let's reach to the portal and see what we have there.

06:09

As you can see, we have to resource groups. One is the cyber very cli test resource group.

06:15

We can click on it

06:16

and see that we have the resource is let's look at the deployments. So the 1st 1 that we did manually without the parameters files is still here. But we also have the seal I deaf deployment in the resource group, which is the second deployment that we did

06:33

for these resource group.

06:35

In the production one, we have just a single deployment, which is the production deployment that we have done.

06:44

Now you have learned how you can use the usher cli tow dough arm template deployments