Skip to content

Commit 9acdf9d

Browse files
prajin-opCHERIANS
andauthored
chore: Update documentation (#385)
* chore: Update documentation * Update README.md * Update README.md * Update README.md * chore: Update solution for SIT * chore: Update tfvars for solution SIT * update details of identity provider --------- Co-authored-by: Stephen Cherian <[email protected]>
1 parent 6be88da commit 9acdf9d

35 files changed

+95
-790
lines changed

released/SAP-Inside-Tracks/SITBLR_DEC_2024/exercises/EXERCISE1/README.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -65,10 +65,11 @@ globalaccount = "<YOUR GLOBAL ACCOUNT SUBDOMAIN>"
6565
idp = null
6666
```
6767

68+
6869
The SAP BTP Global Account Subdomain can be found in the SAP BTP Cockpit as shown below
6970
<img width="600px" src="assets/trial-account.png" alt="SAP BTP Global Account Subdomain">
7071

71-
The `idp` (Identity Provider Orgin Key ) is set to null. If a [Custom Identity Provider](https://help.sap.com/docs/btp/sap-business-technology-platform/log-on-with-custom-identity-provider-to-sap-btp-cockpit) is used to login to SAP BTP this value is set to Orgin Key of the Custom Identity Provider`
72+
The `idp` (Identity Provider Orgin Key ) value is set to null. If a [SAP Cloud Identity Services tenant (Custom Identity Provider)](https://help.sap.com/docs/btp/sap-business-technology-platform/log-on-with-custom-identity-provider-to-sap-btp-cockpit) is used to login to SAP BTP Cockpit this value is set to Orgin Key of the Custom Identity Provider`. The orgin key of the SAP Cloud Identity Services tenant can be found in SAP BTP Cockpit. Go to the Global Account where teh Subaccount is being created. Navigate to Security -> Trust Configuration and the orgin key can be found under the Trust Configuration of the Identity Provider.
7273

7374
> [!NOTE]
7475
> We are using here a naming convention of Terraform to define the variable values. The file `terraform.tfvars` is used to define the variable values. The file is not checked into the source code repository. This is important to keep sensitive information out of the source code repository. When you run Terraform, it will automatically load the variable values from this file.

released/SAP-Inside-Tracks/SITBLR_DEC_2024/exercises/EXERCISE1/SOLUTION_EX1/main.tf

Whitespace-only changes.

released/SAP-Inside-Tracks/SITBLR_DEC_2024/exercises/EXERCISE1/SOLUTION_EX1/outputs.tf

Whitespace-only changes.

released/SAP-Inside-Tracks/SITBLR_DEC_2024/exercises/EXERCISE1/SOLUTION_EX1/provider.tf

Lines changed: 0 additions & 16 deletions
This file was deleted.

released/SAP-Inside-Tracks/SITBLR_DEC_2024/exercises/EXERCISE1/SOLUTION_EX1/terraform.tfvars-sample

Lines changed: 0 additions & 1 deletion
This file was deleted.

released/SAP-Inside-Tracks/SITBLR_DEC_2024/exercises/EXERCISE1/SOLUTION_EX1/variables.tf

Lines changed: 0 additions & 7 deletions
This file was deleted.

released/SAP-Inside-Tracks/SITBLR_DEC_2024/exercises/EXERCISE2/SOLUTION_EX2/main.tf

Lines changed: 0 additions & 20 deletions
This file was deleted.

released/SAP-Inside-Tracks/SITBLR_DEC_2024/exercises/EXERCISE2/SOLUTION_EX2/outputs.tf

Lines changed: 0 additions & 9 deletions
This file was deleted.

released/SAP-Inside-Tracks/SITBLR_DEC_2024/exercises/EXERCISE2/SOLUTION_EX2/provider.tf

Lines changed: 0 additions & 16 deletions
This file was deleted.

released/SAP-Inside-Tracks/SITBLR_DEC_2024/exercises/EXERCISE2/SOLUTION_EX2/terraform.tfvars-sample

Lines changed: 0 additions & 1 deletion
This file was deleted.

released/SAP-Inside-Tracks/SITBLR_DEC_2024/exercises/EXERCISE2/SOLUTION_EX2/variables.tf

Lines changed: 0 additions & 55 deletions
This file was deleted.

released/SAP-Inside-Tracks/SITBLR_DEC_2024/exercises/EXERCISE3/README.md

Lines changed: 12 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -40,20 +40,26 @@ We define a complex variable type, which is a [list](https://developer.hashicorp
4040

4141
## Step 2: Add the variable to the tfvars file
4242

43-
Now we need to specify the entitlements we want to create to the `terraform.tfvars` file.
43+
Now we need to specify the entitlements we want to create to the `terraform.tfvars` file.
4444

45-
We want to add the following entitlements to the subaccount:
46-
47-
- `sapappstudiotrial` application with the `trial` plan
48-
49-
Open the `terraform.tfvars` file and add the following code:
45+
If you are creating subaccount in **SAP BTP Trial landscape**, open the `terraform.tfvars` file and add the following code:
5046

5147
```terraform
5248
bas_service_name = "sapappstudiotrial"
5349
bas_plan = "trial"
5450
5551
bas_developers = ["[email protected]", "[email protected]"]
5652
```
53+
OR
54+
55+
If you are creating Subaccount in **Live or Production landscapes** such as `EU10`, `US10`, `AP10` etc, open the `terraform.tfvars` file and add the following code:
56+
57+
```terraform
58+
bas_service_name = "sapappstudio"
59+
bas_plan = "standard-edition"
60+
61+
bas_developers = ["[email protected]", "[email protected]"]
62+
```
5763

5864
## Step 3: Add the entitlements configuration
5965

released/SAP-Inside-Tracks/SITBLR_DEC_2024/exercises/EXERCISE3/SOLUTION_EX3/main.tf

Lines changed: 0 additions & 55 deletions
This file was deleted.

released/SAP-Inside-Tracks/SITBLR_DEC_2024/exercises/EXERCISE3/SOLUTION_EX3/outputs.tf

Lines changed: 0 additions & 9 deletions
This file was deleted.

released/SAP-Inside-Tracks/SITBLR_DEC_2024/exercises/EXERCISE3/SOLUTION_EX3/provider.tf

Lines changed: 0 additions & 16 deletions
This file was deleted.

released/SAP-Inside-Tracks/SITBLR_DEC_2024/exercises/EXERCISE3/SOLUTION_EX3/terraform.tfvars-sample

Lines changed: 0 additions & 5 deletions
This file was deleted.

released/SAP-Inside-Tracks/SITBLR_DEC_2024/exercises/EXERCISE3/SOLUTION_EX3/variables.tf

Lines changed: 0 additions & 91 deletions
This file was deleted.

released/SAP-Inside-Tracks/SITBLR_DEC_2024/exercises/EXERCISE4/README.md

Lines changed: 10 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -53,12 +53,20 @@ resource "btp_subaccount_environment_instance" "cloudfoundry" {
5353
```
5454
### Step 2: Add the variables to tfvar file
5555

56-
Add following variables to your `tfvars` file to configure the CloudFoundry Plan.
56+
If you are creating subaccount in **SAP BTP Trial landscape**, open the `terraform.tfvars` file and add the following variable:
5757

5858
```terraform
5959
cf_plan = "trial"
6060
```
61+
**OR**
62+
63+
If you are creating subaccount in **Live or Production landscapes** such as `EU10`, `US10`, `AP10` etc, open the `terraform.tfvars` file and add the following variable:
64+
65+
```terraform
66+
cf_plan = "standard"
67+
```
6168
Save the changes.
69+
6270
### Step 3: Adjust the output variables
6371

6472
As we are using the output variables, we need to adjust the output variables in the `outputs.tf` file. Open the `outputs.tf` file and add the following code:
@@ -99,4 +107,4 @@ output "cloudfoundry_org_name" {
99107

100108
You've now successfully created a Cloud Foundry environment instance as well as a Cloud Foundry space in SAP BTP.
101109
102-
Continue to - [Exercise 5 - Create a CloudFoundry Space](../EXERCISE5/README.md).
110+
Continue to - [Exercise 5 - Create a CloudFoundry Space](../EXERCISE5/README.md).

0 commit comments

Comments
 (0)