org-formation/org-formation-cli

org formation support specific CDK stack to deploy

lielran opened this issue · 3 comments

lielran commented

it seems that org formation is using --all to deploy all stacks. it would be nice to have a parameter to control on which stack to deploy (with default of all)

org-formation-cli/src/plugin/impl/cdk-build-task-plugin.ts

Line 155 in 78f7fbe

const commandExpression = { 'Fn::Sub': 'npx cdk destroy --all --require-approval=never ${CurrentTask.Parameters}' } as ICfnSubExpression;

dannysteenman commented

I've currently solved it for myself by specifying the stack name in the customdeploycommand:

CustomDeployCommand: !Sub AWS_REGION=${AWS::Region} npx cdk deploy --app "ts-node ./src/main.ts" "*gitlab-oidc" --require-approval never
lielran commented

Oh nice!
We just lunch org-formation cdk support and plan to run all the stacks because of this limitation.
it also can prevent us the usage of npx since we already have cdk installed on the node modules and local folders

lielran commented

closed since there is a valid workaround