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
The following quote from the repository readme pretty much makes sense also for Takomo:
90% of everything CDK does is at "compile-time", when the templates are being rendered. It has a very limited ability to execute custom code at deployment time, and never really between the deployments of custom stacks and resources. Furthermore, its way of wiring together stacks uses CloudFormation exported outputs and imports, which are rather rigid and can have a host of unintended consequences, especially when values might change.
In contrast, Sceptre is a deployment orchestration tool. It excels in deploying entire environments of stacks, "wiring them together"
The key benefit from using Takomo could be native support for Typescript whereas Sceptre supports tight integration with Python defined CDK classes.
Yeah, I've been working with CDK a lot lately and can agree with the Sceptre team's findings. I guess I should revisit the idea of integrating CDK now that I have gained more understanding of its workings.
It would be cool to integrate CDK somehow to Takomo.
The text was updated successfully, but these errors were encountered: