Control Tower Pipeline Testing Strategy about aws-control-tower-customizations HOT 4 CLOSED

Please let us know if additional information needed, thanks

from aws-control-tower-customizations.

Hello @sasiki-coder Thanks for reaching out to us. Can you please elaborate the first use case? Are you testing the templates in the add-on? Or wish to test the add-on manifest artifacts?
For the templates in the add-on, we recommend you to use stack set console to deploy the stack instances.
If you are testing add-on, the validation (build) stage should be able to catch any json/yaml/schema issues.

With respect to separate pipeline for testing, development and production, is your preference to use same org master account or does separate org master account per environment works? Please advise. Thanks in advance.

from aws-control-tower-customizations.

Its the add-ons testing. Ideally we want to see speed up the testing process currently its taking ~1 hr to test the changes.

Also I see the pipeline execution is sequential not parallel, is there configuration that can be specified in manifest.yaml or somewhere to make it parallel execution ?

My current preference is to use same org master account, would want to isolate from development to production for testing any changes.

Thanks

from aws-control-tower-customizations.

@sasiki-coder The current release does not support any setting that can change the sequential stack set deployment to parallel to avoid any issues if there is a dependency between stack sets.

from aws-control-tower-customizations.