feat: add multi-org generate_params.py

docs/user-guide.md

@@ -646,13 +646,16 @@ each account under that OU.
 deployment map as a target. If only the account number is in the deployment map
 the corresponding OU parameter file will not be referenced.
 
+
+
 ```txt
 global.yml
-└───deployment_account_region.yml (e.g. global_eu-west-1.yml)
-    └───ou.yml (e.g. ou-1a2b-3c4d5e.yml)
-        └───ou_region.yml (e.g. ou-1a2b-3c4d5e_eu-west-1.yml)
-            └───account.yml (e.g. dev-account-1.yml)
-                └───account_region.yml (e.g. dev-account-1_eu-west-1.yml)
+└───deployment_org_stage.yml (e.g. global_dev.yml)
+  └───deployment_account_region.yml (e.g. global_eu-west-1.yml)
+      └───ou.yml (e.g. ou-1a2b-3c4d5e.yml)
+          └───ou_region.yml (e.g. ou-1a2b-3c4d5e_eu-west-1.yml)
+              └───account.yml (e.g. dev-account-1.yml)
+                  └───account_region.yml (e.g. dev-account-1_eu-west-1.yml)
 ```
 
 This concept also works for applying **Tags** to the resources within your
@@ -712,6 +715,28 @@ the root of the repository.
 *Note:* Currently only Strings type values are supported as parameters to
 CloudFormation templates when deploying via AWS CodePipeline.
 
+**CloudFormation Parameters in a Multi-Organization ADF Setup** 
+The CloudFormation Parameter generation feature is fully compatible with 
+the [Multi-Organization ADF Setup](./multi-organization-guide.md) approach. 
+Let's assume that we have a three AWS Org setup with a dev, int and prod 
+AWS Organization. This implies that the SSM param `/adf/org/stage` will have 
+one of the following three values: `[dev, int, prod]`; depending on the AWS 
+Organization you are in. Let's further assume that your application in scope 
+requires AWS Organization specific parameters.In that case, the `params` should 
+have the following content: 
+
+```txt
+params
+└───global_dev.yml
+└───global_int.yml
+└───global_prod.yml
+└───global.yml
+```
+
+When the application gets deployed, ADF will choose the right parameter file 
+based on the value of the SSM prameter "/adf/org/stage".
+
+
 ### Serverless Transforms
 
 If the template that is being deployed contains a transform, such as a

src/lambda_codebase/initial_commit/bootstrap_repository/adf-build/shared/generate_params.py

@@ -118,6 +118,7 @@ class PipelineDefinition(TypedDict):
 DEPLOYMENT_ACCOUNT_REGION = os.environ["AWS_REGION"]
 PROJECT_NAME = os.environ["ADF_PROJECT_NAME"]
 EMPTY_PARAMS_DICT: ParametersAndTags = {'Parameters': {}, 'Tags': {}}
+ADF_ORG_STAGE = os.getenv("ADF_ORG_STAGE", "dev")
 
 
 class Parameters:
@@ -229,6 +230,7 @@ def create_parameter_files(self) -> None:
                 i.e. "/devsecops/security_eu-west-1"
             1. f"{organization_unit_path}" i.e. "/devsecops/security"
             1. f"{global}_{region}" i.e. "global_eu-west-1"
+            1. f"{global}_{stage}" i.e. "global_dev"
             1. f"{global}" i.e. "global"
 
         It will then generate a JSON file that holds all the parameters per
@@ -299,6 +301,15 @@ def create_parameter_files(self) -> None:
                     ),
                     current_params
                 )
+                # Compare account_region final to global_stage
+                adf_org_stage = ADF_ORG_STAGE # Fetch from Environ for Start
+                current_params = self._merge_params(
+                    Parameters._parse(
+                        params_root_path=self.cwd,
+                        params_filename=f"global_{adf_org_stage}",
+                    ),
+                    current_params
+                )
                 # Compare account_region final to global
                 current_params = self._merge_params(
                     Parameters._parse(