docs: update READMEs

Author: lechnerc77

sample-setup/README.md

@@ -17,6 +17,14 @@ We follow the paradigms of a simpel and clear Terraform configuration as laid ou
 
 Ensuring naming conventions is one import aspect when provisioing and managing your SAP BTP account. We will align our samples in accordance to the [Naming Conventions for SAP BTP Accounts](https://help.sap.com/docs/btp/btp-admin-guide/naming-conventions-for-sap-btp-accounts).
 
-To ensure consistent naming of your resources, we encapsulate the guidlines in a dedicated module.
+To ensure consistent naming of your resources, we encapsulate the guidlines in dedicated module. Besides the naming we will also include the labels that can be attached to some resources on SAP BTP.
 
-Besides the naming we will also include the labels that can be attached to some resources on SAP BTP.
+We have created one module for the level of the [directory](./modules/sap-btp-naming-conventions-directory/README.md) and one for the level of the [subaccount](./modules/sap-btp-naming-conventions-subaccount/README.md).
+
+## Setup of Directories
+
+The setup of directories as a structuring element for the subaccounts is configured in the folder `basic-setup/directory-setup`. The Details about the setup are described in the [README.md](./basic-setup/directory-setup/README.md) file.
+
+## Setup of Subaccounts
+
+The setup of subaccounts is configured in the folder `basic-setup/subaccount-setup`. The Details about the setup are described in the [README.md](./basic-setup/subaccount-setup/README.md) file.

sample-setup/basic-setup/directory-setup/README.md

@@ -5,18 +5,21 @@
 - We assume that we use the directories as structuring element for the subaccounts i.e., un an unmanaged fashion.
 - We assume that we do the directory setup in one run for all involved departments.
 
-## Design Decsion
+## Design Decsions
 
-We decouple the directory creation i.e., the setup of the basic structure from the creation of the operational units namely the subaccounts inside of the directory. The changes on directory level are probably a rare sceanrio compared to the subaccounts (depending on their stage) and we therefore want to avoid side effects as well as lengthy state refreshes.
+We decouple the directory creation i.e., the setup of the basic structure from the creation of the operational units namely the subaccounts inside of the directories. The changes on directory level are probably a rare sceanrio compared to changes in the subaccounts additionally depending on their stage. We want to avoid side effects as well as lengthy state refreshes and keep the state of the directories seperate.
 
 ## Directory Setup
 
-We will create directories for the following departments:
+The creation of the directories is steered by a map of objects that define the business data relevant for a directory namely:
 
-- HR
-- Sales
-- Finance
+- business_unit (`string`): The business unit that owns the directory e.g., HR, IT, Finance
+- costcenter (`string`): Cost center of the business unit
+- directory_contacts (`list(string)`): List of email addresses representing the directory contacts
+- region (`string`): The geographical region of the directory e.g., EMEA
 
-In addition we create a directory for shared services.
+This is input data is reflected by the variables defined in the [variables.tf](./variables.tf) file
 
-All directories are located in EMEA.
+The directories are provisioned via the [main.tf](./main.tf) file which delegates to the module [base-directory-setup](../../modules/base-directory-setup/README.md). This module combines the corresponding module containing the naming and labeling conventions for a directory and calls the Terraform resource [btp_directory](https://registry.terraform.io/providers/SAP/btp/latest/docs/resources/directory).
+
+After provisioning the output summarizes the executed setup as given by the [outputs.tf](./outputs.tf) file.

sample-setup/basic-setup/subaccount-setup/README.md

@@ -1,8 +1,27 @@
 # Setup of a Subaccount
 
+## Assumptions
+
+- We assume that we use the directories as structuring element for the subaccounts i.e., un an unmanaged fashion.
+- We assume that we do the directory setup in one run for all involved departments.
+
+## Design Decsions
+
+We decouple the directory creation i.e., the setup of the basic structure from the creation of the operational units namely the subaccounts inside of the directory. The changes on directory level are probably a rare sceanrio compared to the subaccounts (depending on their stage) and we therefore want to avoid side effects as well as lengthy state refreshes.
+
+## Subaccount Setup
+
 - Basic setup of a subaccount. Every subaccount is created seperately
 - Naming Conventions and Labels
 - Validation of Geo Region and Subaccount region
 - Default Setup of custom IdP
 - Provision CF env (optional)
 - Execute default plus à la carte entitlements
+
+### Validations for Geographies and BTP Regions
+
+### Trust Configuration for Custom IdP
+
+### Setup of Entitlements
+
+### Setup of Cloud Foundry Environment