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
At the moment, we support strictly sequential processing of all listed stacks (and their corresponding contexts and environments)
However, this may be considered as a constraint when multiple stacks that are independent of each other need to be processed. This results in an increased time-to-completion when processing multiple stacks, and also indirectly limits provisioning actions on "later" stacks, when, for example, there are errors provisioning "earlier" stacks (due to the current 'fail-fast' behavior)
When stacks are entirely unrelated, it is prudent to let them provision, despite the failure of provisioning actions on other stacks.
Some stacks within a group of stacks may rely on the successful provisioning of other stacks (for example: due to cross-stack references between stacks) that "precede" them.
However, there may be multiple groups of stacks, such that each group forms a "closure" of stacks that either impact or are impacted by provisioning of other stacks within the same group. Again, groups may be completely independent of each other, or there my be a precedence between groups that must be provisioned in some order.
Similarly, some form of "concurrency control" is desirable that lets the user control how many such stacks can be provisioned in parallel.
(Suggestion: attempting to use with space-odyssey may be an interesting exercise to test this)
The text was updated successfully, but these errors were encountered:
At the moment, we support strictly sequential processing of all listed stacks (and their corresponding contexts and environments)
However, this may be considered as a constraint when multiple stacks that are independent of each other need to be processed. This results in an increased time-to-completion when processing multiple stacks, and also indirectly limits provisioning actions on "later" stacks, when, for example, there are errors provisioning "earlier" stacks (due to the current 'fail-fast' behavior)
When stacks are entirely unrelated, it is prudent to let them provision, despite the failure of provisioning actions on other stacks.
Some stacks within a
group
of stacks may rely on the successful provisioning of other stacks (for example: due to cross-stack references between stacks) that "precede" them.However, there may be multiple
group
s of stacks, such that each group forms a "closure" of stacks that either impact or are impacted by provisioning of other stacks within the samegroup
. Again,group
s may be completely independent of each other, or there my be a precedence between groups that must be provisioned in some order.Similarly, some form of "concurrency control" is desirable that lets the user control how many such stacks can be provisioned in parallel.
(Suggestion: attempting to use with space-odyssey may be an interesting exercise to test this)
The text was updated successfully, but these errors were encountered: