<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

Applying the Terraform Setup to SAP BTP

Lesson Content

Getting Started with Terraform on SAP BTP

SAP_MOOC_terra1_unit3_lesson2_APPLY_Video.mp4

Hello and welcome back to Unit 2 setting up your first Terraform configuration. We are now in lesson 2 and we want to apply our Terraform setup to the SAP Business Technology platform. Looking at our journey, we already made some progress. We are now making the third step in our journey, we set up our subaccount. So what will we learn throughout this lesson? We already saw the basic Terraform flow. We will now dive a bit deeper and look at the generic Terraform flow that you should apply when you configure infrastructure as code via Terraform. Then we will talk a bit about using good practices to create your first Terraform script. Finally, that's what we are all waiting for. We will create our first asset, our first infrastructure, namely a subaccount on SAP BTP. Having said that, how does this generic flow that we want to use look like, Rui? That's a fantastic question. Let's maybe do a quick recap on what we heard in the lessons before. Terraform has three core flows. So the first step is about authoring, meaning authoring the infrastructure as code, and with that defining the target state of your infrastructure. In the plan step, Terraform provides you a plan how this target will be reached. With that, you can preview the changes before applying them. In the apply step, we tell Terraform to apply the plan, and to provision the infrastructure in a reproducible way. So these are the three main steps. But in day-to-day work, you should make use of additional commands which make your life much easier. The init command triggers Terraform to fetch the necessary Terraform provider information as well as all Terraform functions that your Terraform script uses. With the format document, or FMT, in short, you can tell Terraform to format your code properly, which makes it also better readable. This is specifically good when you're sharing that code with other colleagues. It's also good to use validate as a command with Theraform. It checks a code for syntactical correctness before trying to run the plan command. Apply the changes and you will either be informed about syntax errors or you get the information that your code is all good. And now another important command, the destroy command which of course you should always use very wisely because that actually takes a terraform plan and execute it backwards meaning it takes the infrastructure that you have and then deprovisions all the resources backwards so in case it will delete all the entitlements your related sub account and all your labels you have assigned and something you should be always aware of So these were the additional commands. And I think, Christian, we will now use some of them in our hands-on part, right? Exactly. That's what we will do. We start training our muscle memory using the commands that you just brought up. We will, of course, first have to write the configuration for the subaccount on SAP BTP, and then we will walk through the commands as you just laid them out. We will format the code. we will initialize Terraform, we will then validate the code, and then we will do our first plan and apply phase in order to see what Terraform wants to do, and finally set up the subaccount. So, let's make our hands dirty. Okay, so here we are now in our Read Me MD for Unit 2, Lesson 2 in the GitHub repository, to apply the Terraform set up on BTP, and what do we need to do to set up to set up? up now a subaccount and the best way to learn how to do this is actually looking into the respective documentation, right? Exactly. So we have already been in the documentation when we configured our provider and now we can make one step forward. What do we want to do? We want to create a subaccount and as we heard before the right asset of Terraform is a resource. And if we open the resource tree here, we see there are a lot of resources that are supported by the BTP provider, but the one that we want to see is BTP subaccount resource. And yeah, cool, we have an example usage here, which tells us how to set up a subaccount with some parameters, but what do we want to do exactly? So we want actually to create the subaccount with a specific name. we want to assign it a subdomain and then in addition having the beta features enabled and then last but not least adding two labels where we actually add the key stage and the key cost center to that subaccount which helps our target persona to assign the subaccount to a specific cost center which is actually helpful to do some cross-charging. It's something also we see a lot with the customers that we talk to, right, that they have these mechanisms in place. Those are kind of the typical labels that we see. Now let's check again the documentation if that's all there. So if we scroll down, we see the schema, so the input parameters that we can't hand over to this resource. And we see the ones that we are looking for. We have the name, the subdomain. Of course we have a region because the subaccount lives in a dedicated region. And in the optional section, we have the beta-enabled parameter. Cool. That's what we want to see. It's a Boolean, as expected. And we have labels, which is a map of set of strings. That's quite a mouthful, but we will see that that's not so complicated to create that one. Yeah. So I think what we can do now is simply just take from our documentation that we wrote for this unit, the respective section here, resource BTP subaccount. We provide it with a name called Project Sub-Account that you will use. And then we are assigning all the required parameters, name, sub-domain region. And then we add the beta-enabled flag as well as the labels. So that's something we now just can copy and paste it to a new file. Right. But before we do so, one more thing. So we created this directory learning terraform SAP BTP in the home directory of VS code. So as we see here from the previous lesson, we have Provider.tf, but we don't see it here in the Explorer, right? So what we want to do is we want to add the folder to the workspace that we are just using. And what we do is we use the home directory of VS code. because that's where we located all the stuff, and we say, okay, and here we go. We already see the directory with the provider TF in our Explorer. Now, as you said, and as the documentation points out, we want to have a new file, which contains the configuration, and we call that main.tf. That's the best practice to call it that way, right? That's definitely a good practice to call it main.tf, because that's, domain configuration. Now let's copy this code over. And yeah, we see as you just laid out, we take the resource BTP sub account. We have to give it a name or an address in order to later use it. And then we have our obligatory or mandatory parameters, name subdomain region. We set it to US 10. Be aware we are on the trial landscape. So you just have US 10 and AP21 as regions. Then we enable the better features. And then as you can see here, we have these labels which had this fancy type. It's basically a key value pair, so we have the key stage, the key cost center. And then we have a map because we can add or a set because we can add multiple strings to one label. And with that, I think we're good to go, right? That's all for the infrastructure as code piece. And now I think it's time to go through our Terraform commands we just learned. Absolutely. So let's train our muscle memory. First things first, we need to initialize the directory. So the Terraform knows, hey, this is a directory where Terraform code lies, and that's Terraform init. Now, there is now something going on. As you can see, the important part is it's initializing the provider plugins. So what it does is it's really downloading the plugins. And you can see that here in the outline of the directory, we now have a terraform directory and a Terraform.log file. And we see within the .terraform directory we have our provider binary. Cool. What comes next? Well, formatting. Formatting. So did we do everything nicely in a good and readable way? Let's see, Terraform FMT looks good.  So if there would be some changes, the file would be laid out where the changes happened. And then when we have formatted everything, I think validation makes sense, right? Yeah, to see if we have any syntactical errors in our code. Now be aware, this is static validation. Yes, of course. It's not dynamically, so it's just checking, hey, is everything in place? But it cannot say if there are some issues when called, the API, of course. Everything you can do before actually applying this to the infrastructure. So it looks good. Looks good to me, then now it's getting serious. So we do the Terraform planning. And we add one parameter here, the minus out parameter, which stores the result of the planning so that we can reuse it later in the apply phase. So, let's see what happens now. Okay. Exactly what we expected. So we see how, for example, the beta enabled feature was set to true. We see the labels listed, the cost center and the stage. We see as well the name, the region, and the subdomain setup. And for several others you see known after apply, because why? Something that you will actually get once it is applied, which we haven't done so far, because we just went through the planning phase. That's right. Then Terraform is already so kind to tell us, hey, if you want to apply it, use this command and we copy that. Let me clear. And now, let's see what happens. The sub-account creation started. Meaning also the authentication is working? Exactly. That's what I wanted to say. So if you run into an error here telling you, client could not be created, then probably your authentication data is not correct, so you have to check that. So the BTP password or BTP username was not set correctly, but in our case it looks like the subaccount has been successfully created. In record time, 21 seconds. So let's check it. Let's jump to our... Just reload it again. Global account and let's see what we have. And indeed there is a subaccount listed here. In the region US East, that's US 10. That's US 10. So let's jump into it. And yeah, you said already regions there. We have the beta features enabled, cool. That's what we wanted. And we have labels and they are set to the value that we wanted to have, right? Yes. We were successful. High five. Indeed. So, as you can see, within the ReadMe, we have also laid out each and every step that we just went through. So you can see it including the output. And with that, I think we already did our first terraform configuration. Perfect. Okay. Now we are back again from our hands on exercise. What are the key takeaways you can take with you now? You experienced how Terraform enables you to efficiently write and manage infrastructure as code on SAP Business Technology Platform. You saw as well that it's really easy to create a subaccount on SAP BTP with Terraform, and in the next lesson, we will go even deeper. See you there. Bye-bye.