You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: released/SAP-Inside-Tracks/SITBLR_MAR_2025/exercises/EXERCISE1/README.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -97,7 +97,7 @@ variable "costcenter" {
97
97
variable "org_name" {
98
98
type = string
99
99
description = "Defines to which organization the project account shall belong to."
100
-
default = "HandsOn"
100
+
default = "Exporter"
101
101
}
102
102
variable "bas_admins" {
103
103
type = list(string)
@@ -310,6 +310,6 @@ terraform apply
310
310
311
311
## Summary
312
312
313
-
You've now successfully created a SAP BTP Subaccount with active resources, We will export this Subaccount using BTP Terraform exporter.
313
+
You have successfully created an SAP BTP Subaccount with active resources using Terraform. Now, imagine you already have an existing subaccount and want to bring it under Terraform's management. This exercise will guide you through that process.
314
314
315
315
Continue to - [Exercise 2 - Export BTP Subaccount Using BTP Terraform Exporter](../EXERCISE2/README.md).
If you want any of the resources (Entitlements, Role collections, Roles, etc) to be excluded from the Subaccount that you are going to export, Remove them from the `btp_resource_<subaccount_id>.json`.
34
+
If you want any of the resources (Entitlements, Role collections, Roles, etc) to be excluded from the Subaccount that you are going to export, Remove them from the `btp_resources_<subaccount_id>.json`.
35
35
36
36
You should see the `btp_resource_<subaccount_id>.json` like below:
37
37
@@ -51,7 +51,7 @@ You should see the following output:
51
51
52
52
<imgwidth="600px"src="assets/exportbyjson.png"alt="export by json output">
53
53
54
-
## Export the resources
54
+
## Export the BTP resources
55
55
56
56
You can go the the `generated_configurations` folder, There you will see all the generated scripts.
57
57
@@ -64,21 +64,41 @@ You should see the below output:
Now all the resources are exported and you can see the stae file under the folder `generated_configurations_<subaccount_id>`
67
+
Now all the resources are exported and you can see the state file under the folder `generated_configurations_<subaccount_id>`
68
68
69
69
> [!TIP]
70
70
> If you do not want to use Json file input, You can also use the `btptf export -S <subaccount_id>` command to export all the resources under one Subaccount.
71
71
72
+
## Export Cloudfoundry resources
73
+
74
+
To export Cloud Foundry resources, we use the Organization's ID.
75
+
76
+
As we did in the previous BTP export, we will first create the JSON file. However, this time, we only want to export the spaces. To do this, run the following command:
77
+
78
+
```bash
79
+
btptf export --organization < Organization ID > --resources spaces
This command will generate the configuration files under `generated_configurations_<organization_ID>`.
86
+
87
+
In this case, we are exporting all spaces from the Cloud Foundry organization, and we do not need to provide a JSON file as input.
88
+
89
+
72
90
### Summary
73
91
74
92
Congratulations! You have successfully completed the hands-on exercise.
75
93
76
-
This demonstrates how the BTP Terraform Exporter can be used to bring an existing BTP Subaccount under Terraform management. Without this tool, these tasks would be cumbersome and prone to errors.
94
+
This demonstrates how the BTP Terraform Exporter can be used to bring an existing BTP Subaccount under Terraform management. Without this tool, managing these tasks would be cumbersome and more susceptible to errors.
0 commit comments