<p>about your learning experience to help us improve.</p>

You've completed

cleanFiles/bookmap_Getting_Started_with_Terraform_on_SAP_BTP_en-US_learning-sap-com_lsc-prod.zip (MMCP-DROPZONE) - 2025-02-18T09:44:29.000Z

Preparing the Setup for Terraform on SAP BTP

Lesson Content

Getting Started with Terraform on SAP BTP

SAP_MOOC_terra1_unit2_lesson3_PREP_NEU_Video.mp4

Welcome back to Unit 1 getting started with Infrastructure's Code, Lesson 3. Now we're starting to prepare the setup for Terraform on SAP BTP. In the last lesson we introduced our journey map that you now see on the slides that we want to follow along. Now we start our journey and make the first step, namely preparing the Terraform setup on our local machine. What do we want to achieve within this lesson? Well, first of all, you should get an overview about the technical performance. that are needed to follow along in the course, especially in the hands-on part. Then we will give you an overview of the different setup options that you have to do the Terraform coding. We will focus on one preferred option that we will talk about later. At the end of this lesson, you will have a setup up and running so that you can start with the Terraform code. In addition, we will also guide you to where you find the code for the lessons. With that, let's start with the prerequisites. Yeah, sure thing. To follow along, you need to have a trial account on SAP BTP. In case you don't have such a trial account, just Google SAP, BTP trial account, and you get the instructions how to get such an account. In addition, you should use an IDE, like for example Visual Studio Code. That's also the one that we will be using throughout the course now. Depending on the IDE that you use, you should have also some kind of syntax highlighting for Terraform, so that whenever there is a syntax error in your script, maybe by mistyping a few commands, that you automatically see them in your IDE. With that, you don't waste too much time in looking for very easy to fix issues. And then you also need to download and install the Terraform command line interface. So these are the prerequisites that you need to have to really go smoothly together with us through the next steps. But there are actually a few options for you to set this all up, Christian. Do you want to explain these options? Yeah, sure. We prepared three options for you to get the setup done for this course. In option one, we will leverage so-called development containers that you can spin up locally and then everything you need is available in that container. There is one prerequisite for this option, namely you must have Docker installed and running to be able to start the dev containers. Option 2 is GitHub code spaces. As we have already said, the code is available on GitHub. Within the GitHub repository, you have these code spaces and you can start them in the browser using the same configuration as for the dev container. For this option, you need to have a GitHub user. And finally, option 3 is a local setup. You can of course do everything locally and install everything on your machine and work from there. All options are described in detail in the GitHub. GitHub repository we will mention in a second. We will now focus on the dev container setup. Shall we take a look how this works, Rui? Yeah, sure, Christian. We will walk you through the setup with the dev container. The option that we will use in our exercises. We will as well validate if all the prerequisites are met so that we can then go into the next lessons. Maybe just as a side note before we will start, don't be worried. You don't have to type everything on your own that you will see on the screen in the next lessons. We have all the code for that and for all the lessons and exercises on GitHub. So that's something we will share with you. We recommend that you should clone the repository to follow along the steps with us during the next units. And with that, let's now go into the system. So, here we are now on the GitHub repository for our course, and what Christian is just sharing here is the repository itself, and if we scroll a little bit down, you see also what we explained before, the prerequisites, and also explaining, again, the content structure. And in the context structure, we already see now for the Unit 1, Lesson 3, the preparing, the preparation, of our Terraform setup here on your machine and describing actually now what we need to do. So as a first Christian, we need to clone the repository first, correct? Exactly. So on your machine, on your local machine, you can execute exactly this command to clone the repository so that you have everything locally on your machine. Then we have the command here. You also find this URL if you go to the repository and click on this code button and then you see here we have exactly the clone URL. And then in the IDE you just type Git, clone and add the URL for that. And here you go. And now we come to the options that we just mentioned. So the Dev Container Options is the one that is recommended. We will go into detail in a second. The other two are also described here within the repository. One is GitHub Codespaces, which you can directly start by pressing this button. You then have to do some configuration which is described here and you're good to go. And last but not least, you can also do a local installation that is described here. Depending on your operating system, you have to install the Terraform CLI, use the editor of your choice, and that's it. But to make our lives easier, we will go into the recommended option for this course by using the Dev Container setup. And I think what you already did is actually cloning the repository on your IDE, Christian. That's the case. So we have the repository cloned in our pre-fought IDE, the Visual Studio Code. And we also have the Terraform extension installed here. Now, that's important for a local setup. We will now use the DEV container. For the DEV container, we provide the configuration that you need in order to get started without wrapping your head about any dependencies. There are two options for that. We have a DEV container that you start up. And then there is one that injects an environment file, this DEV container.m file, where you can put in your credentials. that you will need in the next lesson in order to authenticate. We will highlight that in the next lesson. Now, how do you get started from this setup? You have cloned everything. Now, in Visual Studio Code, you have this little blue button, open a remote connection. And here you have the option reopen in container. Maybe as a small side comment, so in case you don't have installed the Dev Container module on Visual Studio code, this will not show up, right? So that's something you need to remember. So if you want to have this available, this command, you have to have the Dev Container's module installed on your IDE, just as a side remark. Exactly, that's true. So with that, you have this option re-opening container. If it's not there, as we said, you're probably missing the extension. And then, as we have defined the dev container in the repository, you have now the option to either start the dev container without injecting environmental files or with injecting environment files. I will now, as I have to find the environment file, start the dev container with the environment file. And then you have seen that a little bit of logging comes up. Now, if you do this the very, very first time, there is some action going on behind the scenes, downloading of containers. This is something that might take a bit, depending on your connection. But at the end of the day, you will see something like this here at the bottom. You have the dev container started up. And you have the repository again in place. And if you now open a terminal and type in Terraform version, you will see that Terraform the Terraform CLI is already installed up and running and you can start coding. And this is now, you have installed now version 1.10, so this might differ on your machine maybe as well, but try to get one which is up to date. Yeah, so you don't have to wrap your head around that. We will take care of that. We always take the latest Terraform CLI. Yeah, that's a difference, let's say, we're compared to the local setup where you need to install it separately. But here you get everything from one stop shop. Exactly. So if you do it locally, you really have to look at the version. If not, then don't. Now, there is one more thing to mention. And that's also mentioned here in the ReadMe file. As we mentioned said, you need a trial account for SAP BTP. Now, if you start the trial account, there is already one sub-account created. We recommend that throughout this course, remove this sub-account completely because otherwise you might run into conflicts with respect to entitlements, subscriptions that are already there, and so on. So just clean everything up and then get started from scratch. That makes your life so much easier. So please remove everything you have on your trial account. Then you can follow along this course without any issues. Absolutely. So now we are back from the hands-on. Let's recap what we've done in this lesson. First things first, I guess you have seen that the main interaction with Terraform is handled via the Terraform C-L-I. So it's the central prerequisite that you must have installed. For the coding per se, there is no real prerequisite with respect to the editor. You can use the editor of your choice, as we mentioned. It makes sense to also have an extension installed. That does the syntax highlighting, because that makes work much easier. We are using VS code with the corresponding Terraform extension. With respect to the setup, we recommend the setup via the Dev Container that we present it in the hands-on. Of course, all the other options also work, but we will use the Dev Container setup throughout this course. And as you have seen during the hands-on, the code for all lessons is available on GitHub, so you will have an extensive set of ReadMe files that guide you to through the different units and lessons. You find a link to the repository here on the slides. And with that, we are at the end of this lesson. Thanks for watching and looking forward to seeing you in the next lesson. Bye.