Facilitate multiple customization folders within the Account Customization Pipeline

[sarulthas]

Describe the outcome you'd like In the existing AFT account customization pipeline, only a single customization label can be specified in account request yml file. AFT then searches for the corresponding customization folder name and executes the terraform/bash scripts within that folder. Our requirement is to allow the inclusion of multiple customization folder names in the account-request YAML file. This way, the AFT process will sequentially execute all the customizations listed in the account request file, one after the other.

Is your feature request related to a problem you are currently experiencing? If so, please describe. Yes, We need to perform multiple customizations for different accounts, and currently, we face challenges in organizing them based on Organizational Units (OU). For example say, we are maintaining 10 customization folders, and during the account creation process, we aim to apply a diverse set of customizations to various accounts by selecting and combining specific customizations for each account.

Additional context Current possible input in account request file : account_customizations_name = "sandbox" Expected possible input in account request file : account_customizations_name = ["sandbox", "security", "customization_1", "customization_2"]

[snebhu3]

@sarulthas thank you for reaching out. Have you tried applying the approach shown in this example? If yes, is this approach not working out for you?

[sarulthas]

@sarulthas thank you for reaching out. Have you tried applying the approach shown in this example? If yes, is this approach not working out for you?

This approach should work for me. Thank you so much for pointing out this.