You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the latest version of orgformation you introduced maxconcurrenttasks for aws-cdk tasks which is great! However when I try to set the concurrenttasks to e.g. 10 then the deploy fails because cdk.out is locked on 1 tasks causing the other tasks to fail.
Subject of the issue
In the latest version of orgformation you introduced maxconcurrenttasks for aws-cdk tasks which is great! However when I try to set the concurrenttasks to e.g. 10 then the deploy fails because cdk.out is locked on 1 tasks causing the other tasks to fail.
This is the task:
When the task gets deployed:
Your environment
Steps to reproduce
Create a cdk stack, then the cdk task in orgformation and set maxconcurrenttasks to > 1
Expected behaviour
I expect that this feature allows you to deploy cdk stacks simultaneously on multiple accounts in parallel when MaxConcurrentTasks > 1.
Actual behaviour
cdk.out gets locked (normal cdk behaviour) and that causes the other deploys to fail.
Note: this could be solved by having the ability to add
--output
to a randomcdk-<random hash>.out
folderThe text was updated successfully, but these errors were encountered: