Skip to content

Commit 7d95902

Browse files
lechnerc77lechnerc77
authored
chore: update DSAG Betriebstag to latest version (#350)
1 parent 7d5b9b6 commit 7d95902

File tree

14 files changed

+20
-39
lines changed

14 files changed

+20
-39
lines changed

‎released/dsag/betriebstag2024/exercises/EXERCISE1/README.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -27,7 +27,7 @@ terraform {
2727
required_providers {
2828
btp = {
2929
source = "sap/btp"
30-
version = "~> 1.5.0"
30+
version = "~> 1.8.0"
3131
}
3232
}
3333
}
@@ -63,6 +63,6 @@ globalaccount = "<YOUR GLOBAL ACCOUNT SUBDOMAIN>"
6363
6464
## Summary
6565

66-
You've now created a basic setup of the Terraform provider including its configuration.
66+
You've now created a basic setup of the Terraform provider including its configuration.
6767

6868
Continue to - [Exercise 2 - Setup of a subaccount](../EXERCISE2/README.md).

‎released/dsag/betriebstag2024/exercises/EXERCISE1/SOLUTION_EX1/provider.tf‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ terraform {
33
required_providers {
44
btp = {
55
source = "sap/btp"
6-
version = "~> 1.5.0"
6+
version = "~> 1.8.0"
77
}
88
}
99

‎released/dsag/betriebstag2024/exercises/EXERCISE2/SOLUTION_EX2/provider.tf‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ terraform {
33
required_providers {
44
btp = {
55
source = "sap/btp"
6-
version = "~> 1.5.0"
6+
version = "~> 1.8.0"
77
}
88
}
99

‎released/dsag/betriebstag2024/exercises/EXERCISE3/README.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -76,6 +76,6 @@ You can also check that everything is in place via the SAP BTP cockpit. You shou
7676

7777
## Summary
7878

79-
You've now successfully assigned emergency administrators to the subaccount.
79+
You've now successfully assigned emergency administrators to the subaccount.
8080
8181
Continue to - [# Exercise 4 - Assign entitlements to a subaccount](../EXERCISE4/README.md).

‎released/dsag/betriebstag2024/exercises/EXERCISE3/SOLUTION_EX3/provider.tf‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ terraform {
33
required_providers {
44
btp = {
55
source = "sap/btp"
6-
version = "~> 1.5.0"
6+
version = "~> 1.8.0"
77
}
88
}
99

‎released/dsag/betriebstag2024/exercises/EXERCISE4/SOLUTION_EX4/provider.tf‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ terraform {
33
required_providers {
44
btp = {
55
source = "sap/btp"
6-
version = "~> 1.5.0"
6+
version = "~> 1.8.0"
77
}
88
}
99

‎released/dsag/betriebstag2024/exercises/EXERCISE5/SOLUTION_EX5/provider.tf‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ terraform {
33
required_providers {
44
btp = {
55
source = "sap/btp"
6-
version = "~> 1.5.0"
6+
version = "~> 1.8.0"
77
}
88
}
99

‎released/dsag/betriebstag2024/exercises/EXERCISE6/README.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -44,7 +44,7 @@ For this hands-on we will focus on the *second case*.
4444

4545
Terraform offers dedicated commands in order to adjust the state We will use the `terraform plan -refresh-only` and `terraform apply -refresh-only` commands to detect the drift and adjust the state in Terraform to match the actual state in the SAP BTP cockpit.
4646

47-
First we check the drift with `terraform plan` and add the `--refresh-only` flag to trigger the planning mode for [state replacement](https://developer.hashicorp.com/terraform/cli/commands/plan#planning-modes):
47+
First we check the drift with `terraform plan` and add the `-refresh-only` flag to trigger the planning mode for [state replacement](https://developer.hashicorp.com/terraform/cli/commands/plan#planning-modes):
4848

4949
```bash
5050
terraform plan -refresh-only

‎released/dsag/betriebstag2024/exercises/EXERCISE7/README.md‎

Lines changed: 3 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -8,16 +8,12 @@ In this *optional* exercise you will earn how to create a Cloud Foundry environm
88

99
We want to create a Cloud Foundry environment in the subaccount. We will not directly use the resources of the Terraform provider for SAP BTP, but leverage a concept called [modules](https://developer.hashicorp.com/terraform/language/modules).
1010

11-
Modules are a way to organize Terraform configurations into reusable components. We have a fitting module for the task at hand in this repository. Navigate to the `modules` folder in the root of this repo and you will find the fitting module at [environments/cloudfoundry/envinstance_cf](../../modules/environment/cloudfoundry/envinstance_cf/README.md).
11+
Modules are a way to organize Terraform configurations into reusable components. We have a fitting module for the task at hand in this repository. Navigate to the `modules` folder in the root of this repo and you will find the fitting module at [environments/cloudfoundry/envinstance_cf](../../modules/environment/cloudfoundry/envinstance_cf/envinstance_cf.tf).
1212

1313
Inspect the folder and you will see a known file structure:
1414

1515
- `envinstance_cf_variables.tf`: The file contains the input variables for the module.
16-
- `envinstance_cf.tf`: The file contains the main configuration of the module comprising the resource [`btp_subaccount_environment_instance`](https://registry.terraform.io/providers/SAP/btp/latest/docs/resources/subaccount_environment_instance) of the Terraform Provider for SAP BTP and the resource [`cloudfoundry_org_users`](https://registry.terraform.io/providers/cloudfoundry-community/cloudfoundry/latest/docs/resources/org_users) from the Terraform Provider for Cloud Foundry. It corresponds to the `main.tf` file of a Terraform configuration and also contains the required providers.
17-
18-
> [!NOTE]
19-
> The Terraform provider for Cloud Foundry is a community provider and not maintained by SAP.
20-
16+
- `envinstance_cf.tf`: The file contains the main configuration of the module comprising the resource [`btp_subaccount_environment_instance`](https://registry.terraform.io/providers/SAP/btp/latest/docs/resources/subaccount_environment_instance) of the Terraform Provider for SAP BTP and the resource [`cloudfoundry_org_role`](https://registry.terraform.io/providers/cloudfoundry/cloudfoundry/latest/docs/resources/org_role) from the Terraform Provider for Cloud Foundry. It corresponds to the `main.tf` file of a Terraform configuration and also contains the required providers.
2117
- `envinstance_cf_outputs.tf`: The file contains the output variables for the module.
2218

2319
When taking a closer look at the `envinstance_cf.tf` file, we see that we do not want to implement these steps again. We will re-use the module to create the Cloud Foundry environment.
@@ -232,6 +228,6 @@ You can also check that everything is in place via the SAP BTP cockpit. You shou
232228

233229
## Summary
234230

235-
You've now successfully created a Cloud Foundry environment instance as well as a Cloud Foundry space in SAP BTP.
231+
You've now successfully created a Cloud Foundry environment instance as well as a Cloud Foundry space in SAP BTP.
236232
237233
Continue to - [Exercise 8 - Cleanup](../EXERCISE8/README.md).

‎released/dsag/betriebstag2024/exercises/EXERCISE7/SOLUTION_EX7/provider.tf‎

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -3,11 +3,11 @@ terraform {
33
required_providers {
44
btp = {
55
source = "sap/btp"
6-
version = "~> 1.5.0"
6+
version = "~> 1.8.0"
77
}
88
cloudfoundry = {
9-
source = "sap/cloudfoundry"
10-
version = "1.0.0-rc1"
9+
source = "cloudfoundry/cloudfoundry"
10+
version = "~> 1.0.0"
1111
}
1212
}
1313

0 commit comments

Comments
 (0)