1 00:00:00,360 --> 00:00:08,250 In this video we are going to always Cdcc Commons CDK Toolkit has set of commands that provide to manage 2 00:00:08,250 --> 00:00:15,180 infrastructure code development deployments and the lifecycle all cdcc toolkit command start with the 3 00:00:15,180 --> 00:00:22,680 Cdcc which which is the following by sub commands like Cdcc list cdcc synthesised, cdcc deploy and 4 00:00:22,680 --> 00:00:23,280 so on. 5 00:00:24,000 --> 00:00:31,200 So some of the sub commands have short versions like Els, synth and so on. 6 00:00:31,200 --> 00:00:36,090 That is the the same way the work to CDCR list or synthesize. 7 00:00:36,480 --> 00:00:37,650 This is the evaluation. 8 00:00:37,650 --> 00:00:40,560 I will also show you an options and arguments. 9 00:00:40,560 --> 00:00:48,250 The following sub commands are in any order, so the available commands are summarized from the CDCR 10 00:00:48,300 --> 00:00:49,350 documentation. 11 00:00:49,350 --> 00:00:52,590 If you come this page, I will also share individual resources. 12 00:00:52,590 --> 00:00:55,200 You can find the link in the resource of the lecture. 13 00:00:55,620 --> 00:01:01,560 You can, as you can see that we are in the class development kit version to development quite under 14 00:01:01,560 --> 00:01:01,920 tools. 15 00:01:01,920 --> 00:01:08,820 We have a CDK toolkit toolkit and we will see the all commands with the running CDK. 16 00:01:09,120 --> 00:01:12,120 So there is some CDK toolkit commands. 17 00:01:12,150 --> 00:01:14,010 Let me start with one by one. 18 00:01:14,040 --> 00:01:20,490 As you can see in here, if you scroll down, you can see the toolkit command section and we have a 19 00:01:20,490 --> 00:01:24,090 set of commands that we can run into CDK applications. 20 00:01:24,090 --> 00:01:29,970 The first one is the CDK list and you can use CDK LS for the abbreviation. 21 00:01:29,970 --> 00:01:31,830 What is running the list? 22 00:01:31,830 --> 00:01:34,950 Command and list the stakes in the application. 23 00:01:34,950 --> 00:01:36,660 So what is returning to us? 24 00:01:36,660 --> 00:01:39,540 It is returning to us from the our project code. 25 00:01:39,540 --> 00:01:40,680 Let me show you. 26 00:01:41,760 --> 00:01:42,390 In here. 27 00:01:42,390 --> 00:01:43,950 We have one steak, right? 28 00:01:44,220 --> 00:01:50,340 This will be returned to the Halo Seed case steak when we are running to our CDCR list command. 29 00:01:50,370 --> 00:01:53,160 Let me come back and continue our comments. 30 00:01:53,850 --> 00:02:02,330 And the second comment is CDK synthesize or CDK synthesize and print the colored formation template 31 00:02:02,340 --> 00:02:03,930 for the specified text. 32 00:02:03,930 --> 00:02:11,220 So that means it is basically synthesize or command and converting the cloud formation template or type 33 00:02:11,220 --> 00:02:11,910 secret codes. 34 00:02:11,910 --> 00:02:15,720 It is converting the cloud formation template, YAML or JSON file. 35 00:02:15,750 --> 00:02:21,990 So this is the important command that we are going to use very, very, so much during the course. 36 00:02:22,260 --> 00:02:26,070 And the another command is CDK bootstrap. 37 00:02:26,250 --> 00:02:34,050 It is basically deploys the CDK toolkit staging stack and we will see these bootstrapping bootstrapping 38 00:02:34,050 --> 00:02:36,300 stack in the upcoming videos. 39 00:02:36,300 --> 00:02:43,300 It is also another important command, but we are only one time running this bootstrap before we starting 40 00:02:43,320 --> 00:02:48,090 the CDK applications and the most famous command is CDK deployed. 41 00:02:48,120 --> 00:02:55,860 Of course it is deploying the specified stack into the target environment and also we have a CDK distributed 42 00:02:55,860 --> 00:02:56,250 command. 43 00:02:56,250 --> 00:03:04,080 It is very important because we will be destroy all all provisioned services in one time with only running 44 00:03:04,080 --> 00:03:05,580 the CDK command. 45 00:03:05,610 --> 00:03:07,830 It is very, very important command. 46 00:03:08,660 --> 00:03:10,970 And we have also cbdc development. 47 00:03:11,000 --> 00:03:17,040 It is basically compares the specified stake with the deployed stake or a local cloud formation template. 48 00:03:17,060 --> 00:03:26,570 So it is comparing our local computer and the provisions take on database and start to create different 49 00:03:26,570 --> 00:03:31,550 differences with the target environment and the desired state of the documentation. 50 00:03:32,090 --> 00:03:37,850 And we have also metadata environment displayed the metadata about the specified task. 51 00:03:37,850 --> 00:03:42,290 And we have Cdcc Iron Command we used in the previous videos. 52 00:03:42,290 --> 00:03:49,790 It is basically creates an Cdcc project in the current directory from specified template, we use Cdcc 53 00:03:49,790 --> 00:03:54,110 init EP command with giving to language as a type secret. 54 00:03:54,110 --> 00:03:59,990 So this is also what we are using when starting any creating any cdcc application. 55 00:04:00,290 --> 00:04:08,840 And also we have Cdcc context command which is managed the case case context overviews and we have cdcc 56 00:04:08,870 --> 00:04:11,870 ducks and we have cdcc doctor command. 57 00:04:11,900 --> 00:04:18,320 It is basically check our cdcc application which is any problem or not look very good. 58 00:04:18,320 --> 00:04:22,310 Let's run some cdcc commands on our Helo Cdcc project. 59 00:04:22,310 --> 00:04:28,970 If you come back to our project folder in the Visual Studio code now we are ready for running some cdcc 60 00:04:28,970 --> 00:04:31,970 commands, but we have learned a few minutes ago. 61 00:04:31,970 --> 00:04:37,610 So if we come here, the first commands I would like to run is Cdcc list. 62 00:04:39,260 --> 00:04:45,650 So as I said before, this will be returned to us, or at least from the application now, which is 63 00:04:45,650 --> 00:04:47,850 searching our application and returning to us. 64 00:04:47,870 --> 00:04:54,170 Cyclist Since we have one stick, which is the Halo CD Case Stick, it is returning the disc last name 65 00:04:54,170 --> 00:04:56,600 to us after running the CD command. 66 00:04:56,780 --> 00:05:02,030 So the another command is the important command is CD CDK since command. 67 00:05:05,400 --> 00:05:06,210 In command. 68 00:05:06,240 --> 00:05:07,020 Okay. 69 00:05:07,050 --> 00:05:09,750 Let me hit enter and and see. 70 00:05:09,750 --> 00:05:12,570 The project folder will be changed a little bit. 71 00:05:12,600 --> 00:05:17,190 Hit enter and see that we will generate a document in here. 72 00:05:21,530 --> 00:05:22,030 Okay. 73 00:05:22,190 --> 00:05:22,610 Yes. 74 00:05:22,610 --> 00:05:25,230 CDCR folder is created. 75 00:05:25,250 --> 00:05:29,700 It is very important and you can see the the response from the R command. 76 00:05:29,720 --> 00:05:38,180 So basically see that only metadata is going to create for now since command is basically generate a 77 00:05:38,180 --> 00:05:41,450 document which is the template document. 78 00:05:41,480 --> 00:05:43,240 If you remember from the our. 79 00:05:44,200 --> 00:05:45,430 CD application. 80 00:05:45,700 --> 00:05:52,180 We are running the casing command and this will be create a cloud formation template, YAML or JSON 81 00:05:52,180 --> 00:05:52,820 format. 82 00:05:52,840 --> 00:05:58,350 So I choose a cloud configuration as a demo, so that's why it is returning to me. 83 00:05:58,360 --> 00:05:59,520 YAML Response. 84 00:05:59,530 --> 00:06:09,660 But this is also creating a CDK out folder which is generating a cloud formation template document. 85 00:06:09,670 --> 00:06:14,260 So you can see that we don't have any construct or any resource. 86 00:06:14,260 --> 00:06:17,560 So that's why it is only creating a CDK metadata. 87 00:06:17,560 --> 00:06:22,840 But after that we don't have any creating any other resources case and so on. 88 00:06:22,840 --> 00:06:27,150 But we will see in the upcoming videos, you understand what I'm saying? 89 00:06:27,160 --> 00:06:35,400 This is basically a CD case in code and this will be exporting the class under the CDK out folder. 90 00:06:35,410 --> 00:06:42,670 If we expand this folder, you can see that this will be synthesized the code into the a cloud formation 91 00:06:42,670 --> 00:06:45,940 template using the CDK synth command. 92 00:06:46,860 --> 00:06:52,560 And we can build the synthesise a cloud formation template into terminal. 93 00:06:52,590 --> 00:06:58,170 Also we can see synthesize command under the CDK or folder. 94 00:06:58,260 --> 00:07:02,640 Synthesized templates can also be located within the CDK old folder. 95 00:07:02,730 --> 00:07:05,100 If you open the these. 96 00:07:05,130 --> 00:07:06,260 Hello CDA. 97 00:07:06,810 --> 00:07:07,140 Hello. 98 00:07:07,140 --> 00:07:09,810 Suitcase Tech dot template json file. 99 00:07:09,900 --> 00:07:19,320 You can see the generated CDK template as a JSON format and see all details in here. 100 00:07:19,410 --> 00:07:24,480 Again, we have only created a metadata, so that's why we don't have any resource now. 101 00:07:24,510 --> 00:07:29,340 But we basically see how synthesis is working in the CDK application. 102 00:07:30,090 --> 00:07:30,420 Okay. 103 00:07:30,420 --> 00:07:31,080 Very good. 104 00:07:31,470 --> 00:07:36,720 If you come here and open the our under the left folder, if you open our. 105 00:07:37,600 --> 00:07:40,090 CDK stick+. 106 00:07:41,430 --> 00:07:49,980 So if we uncomment this part and after that run the Cdcc sent command, this scene to command will be 107 00:07:49,980 --> 00:07:54,220 generate a squares queue for the cloud formation template. 108 00:07:54,240 --> 00:08:00,600 If you uncomment and run the case, you can see the auto cdcc output template file will be changed and 109 00:08:00,600 --> 00:08:01,800 adding the screw. 110 00:08:02,130 --> 00:08:04,380 So but I will develop this later. 111 00:08:04,470 --> 00:08:10,620 For now it's okay to see commented and it's okay to see how we can run CDK commands on the CDK application. 112 00:08:10,800 --> 00:08:14,400 And also I would like to show one more command, which is the. 113 00:08:15,420 --> 00:08:17,010 TDK development. 114 00:08:17,190 --> 00:08:24,890 If you hit Enter with CD CD, this will be compared with the target environment and the existing environment. 115 00:08:24,900 --> 00:08:34,740 So since we don't have any services, it's only giving some differences with parameters, conditions 116 00:08:34,740 --> 00:08:35,940 and other changes. 117 00:08:35,970 --> 00:08:37,910 It is basically explain the difference. 118 00:08:37,920 --> 00:08:41,010 We don't deploy in anything from the target M1. 119 00:08:41,010 --> 00:08:46,830 So that's why it is giving some metadata values and which is Apaches and so on. 120 00:08:46,920 --> 00:08:54,180 So this is the CDK dev command that we can also see, which takes an item spill different to our current 121 00:08:54,190 --> 00:08:56,600 account and the target environment. 122 00:08:56,610 --> 00:08:58,830 We can see difference by grouping in here.