Open andreprawira opened 2 weeks ago
I have also experienced this bug using an LZA that was upgraded from v1.8.1 to v1.10. Currently, the only way around this is to set defaults in the CFN template.
If the template has already been provisioned, it must be removed before these can apply.
This bug could be a serious issue for new account that are provisioned within the landing zone causing unexpected results.
I have not included codebuild output as there is no reference the parameters in the output. I would note that the validation phase is still successfully validating that the input parameters are valid for the template provisioned through customization-config.xml so the issue seems to be in the customizations step specifically.
Describe the bug I'm using the LZA to mass CDK bootstrap accounts under an OU. Here is my customizations-config.yaml
and here is my bootstrap-template.yaml
When i commit the code and the pipeline run, the pipeline will finish successfully, the CDK bootstrap stack is also created, the only thing that's missing is that the 4 parameters i'm passing from customizations-config.yaml to bootstrap-template.yaml is never used/consumed and i dont know why. If i hardcode those 4 values accordingly in the default in bootstrap-template.yaml, those values are consumed but we dont want to hardcode them
To Reproduce Add both bootstrap-template.yaml and customizations-config.yaml to your LZA and run it. You should see the pipeline succeed and the stack got deployed under the OU (Testing was my case), but the 4 parameters (TrustedAccounts, TrustedAccountsForLookup, CloudFormationExecutionPolicies, Qualifier) are never consumed/used/passed to the bootstrap-template.yaml
Expected behavior The parameters should be consumed in the template
Please complete the following information about the solution:
Screenshots If applicable, add screenshots to help explain your problem (please DO NOT include sensitive information).