Closed suankan closed 7 months ago
Thank you for bringing this to our attention @suankan. I've gone ahead and made a backlog with the team to align the behavior here.
Hi @balltrev ,
I created a quick fix which might be good to review and include: https://github.com/aws-solutions/aws-control-tower-customizations/pull/127
This is a bug that should be prioritized.
Describe the bug Currently I can specify non-existent OUs in my custom resource when using
deploy_method: stack_set
:The CodeBuild job processes this gracefully by simply omitting the non-existent OU. And this is a desired behaviour because I'm deploying Dev and Prod landing zones from one single
manifest.yaml
where I wanted to just list Dev and Prod OUs.However the CodeBuild job stumbles if I try the same when using
deploy_method: scp
:I'm getting this error in my CodeBuild:
To Reproduce Try to deploy a custom resource and scp policy using the above code examples.
Expected behavior
CodeBuild jobs for both deployment_method
stack_set
andscp
should behave identically when non-existent OUs are found indeployment_targets
. E.g. eitherPlease complete the following information about the solution:
To get the version of the solution, you can look at the description of the created CloudFormation stack. For example, "(SO0089) - customizations-for-aws-control-tower Solution. Version: v1.0.0". You can also find the version from releases
Screenshots n/a
Additional context n/a