aws-control-tower-customizations icon indicating copy to clipboard operation
aws-control-tower-customizations copied to clipboard

Add Existing deployed template to Pipeline

Open anupinder opened this issue 2 years ago • 4 comments

If there is existing templated deployed and bring it to pipeline only way is to remove that template and re add it to pipeline. Is there any workaround ? For certain templates, you cann't delete but at same time want to bring to pipeline.

anupinder avatar Jun 07 '22 15:06 anupinder

Hey @anupinder, just to make sure I've understood your feature request, are you looking to have CfCT "import/ingest" StackSets that you've provisioned external to CfCT?

balltrev avatar Jun 07 '22 23:06 balltrev

At the end of day, you want pipeline to emcompass all stacksets deployed. You described exactly what I am asking and as most organization have stackset and pipeline deployment, it is chaos in long run.

anupinder avatar Jun 09 '22 14:06 anupinder

Sir, This code is running but the control tower will not be able to create it.

krishnamoorthyrajendran avatar Aug 12 '22 06:08 krishnamoorthyrajendran

CfCt has hardcoded "CustomControlTower" keyword for stacksets it creates. If it allows other keywords then it won't try recreate stackset if existing template is added to manifest. Either through some parameter in manifest file or pipeline with default goes to "CustomControlTower".

anupinder avatar Aug 12 '22 12:08 anupinder