In this video we are going to always Cdcc Commons CDK Toolkit has set of commands that provide to manage
infrastructure code development deployments and the lifecycle all cdcc toolkit command start with the
Cdcc which which is the following by sub commands like Cdcc list cdcc synthesised, cdcc deploy and
so on.
So some of the sub commands have short versions like Els, synth and so on.
That is the the same way the work to CDCR list or synthesize.
This is the evaluation.
I will also show you an options and arguments.
The following sub commands are in any order, so the available commands are summarized from the CDCR
documentation.
If you come this page, I will also share individual resources.
You can find the link in the resource of the lecture.
You can, as you can see that we are in the class development kit version to development quite under
tools.
We have a CDK toolkit toolkit and we will see the all commands with the running CDK.
So there is some CDK toolkit commands.
Let me start with one by one.
As you can see in here, if you scroll down, you can see the toolkit command section and we have a
set of commands that we can run into CDK applications.
The first one is the CDK list and you can use CDK LS for the abbreviation.
What is running the list?
Command and list the stakes in the application.
So what is returning to us?
It is returning to us from the our project code.
Let me show you.
In here.
We have one steak, right?
This will be returned to the Halo Seed case steak when we are running to our CDCR list command.
Let me come back and continue our comments.
And the second comment is CDK synthesize or CDK synthesize and print the colored formation template
for the specified text.
So that means it is basically synthesize or command and converting the cloud formation template or type
secret codes.
It is converting the cloud formation template, YAML or JSON file.
So this is the important command that we are going to use very, very, so much during the course.
And the another command is CDK bootstrap.
It is basically deploys the CDK toolkit staging stack and we will see these bootstrapping bootstrapping
stack in the upcoming videos.
It is also another important command, but we are only one time running this bootstrap before we starting
the CDK applications and the most famous command is CDK deployed.
Of course it is deploying the specified stack into the target environment and also we have a CDK distributed
command.
It is very important because we will be destroy all all provisioned services in one time with only running
the CDK command.
It is very, very important command.
And we have also cbdc development.
It is basically compares the specified stake with the deployed stake or a local cloud formation template.
So it is comparing our local computer and the provisions take on database and start to create different
differences with the target environment and the desired state of the documentation.
And we have also metadata environment displayed the metadata about the specified task.
And we have Cdcc Iron Command we used in the previous videos.
It is basically creates an Cdcc project in the current directory from specified template, we use Cdcc
init EP command with giving to language as a type secret.
So this is also what we are using when starting any creating any cdcc application.
And also we have Cdcc context command which is managed the case case context overviews and we have cdcc
ducks and we have cdcc doctor command.
It is basically check our cdcc application which is any problem or not look very good.
Let's run some cdcc commands on our Helo Cdcc project.
If you come back to our project folder in the Visual Studio code now we are ready for running some cdcc
commands, but we have learned a few minutes ago.
So if we come here, the first commands I would like to run is Cdcc list.
So as I said before, this will be returned to us, or at least from the application now, which is
searching our application and returning to us.
Cyclist Since we have one stick, which is the Halo CD Case Stick, it is returning the disc last name
to us after running the CD command.
So the another command is the important command is CD CDK since command.
In command.
Okay.
Let me hit enter and and see.
The project folder will be changed a little bit.
Hit enter and see that we will generate a document in here.
Okay.
Yes.
CDCR folder is created.
It is very important and you can see the the response from the R command.
So basically see that only metadata is going to create for now since command is basically generate a
document which is the template document.
If you remember from the our.
CD application.
We are running the casing command and this will be create a cloud formation template, YAML or JSON
format.
So I choose a cloud configuration as a demo, so that's why it is returning to me.
YAML Response.
But this is also creating a CDK out folder which is generating a cloud formation template document.
So you can see that we don't have any construct or any resource.
So that's why it is only creating a CDK metadata.
But after that we don't have any creating any other resources case and so on.
But we will see in the upcoming videos, you understand what I'm saying?
This is basically a CD case in code and this will be exporting the class under the CDK out folder.
If we expand this folder, you can see that this will be synthesized the code into the a cloud formation
template using the CDK synth command.
And we can build the synthesise a cloud formation template into terminal.
Also we can see synthesize command under the CDK or folder.
Synthesized templates can also be located within the CDK old folder.
If you open the these.
Hello CDA.
Hello.
Suitcase Tech dot template json file.
You can see the generated CDK template as a JSON format and see all details in here.
Again, we have only created a metadata, so that's why we don't have any resource now.
But we basically see how synthesis is working in the CDK application.
Okay.
Very good.
If you come here and open the our under the left folder, if you open our.
CDK stick+.
So if we uncomment this part and after that run the Cdcc sent command, this scene to command will be
generate a squares queue for the cloud formation template.
If you uncomment and run the case, you can see the auto cdcc output template file will be changed and
adding the screw.
So but I will develop this later.
For now it's okay to see commented and it's okay to see how we can run CDK commands on the CDK application.
And also I would like to show one more command, which is the.
TDK development.
If you hit Enter with CD CD, this will be compared with the target environment and the existing environment.
So since we don't have any services, it's only giving some differences with parameters, conditions
and other changes.
It is basically explain the difference.
We don't deploy in anything from the target M1.
So that's why it is giving some metadata values and which is Apaches and so on.
So this is the CDK dev command that we can also see, which takes an item spill different to our current
account and the target environment.
We can see difference by grouping in here.