3 ms·
I wouldn't recommend using cdktf either yet. Can't manage multiple stacks in a single repository, no full support for input variables, constant breaking changes
by yunwal 5y ago
I wouldn't recommend using cdktf either yet. Can't manage multiple stacks in a single repository, no full support for input variables, constant breaking changes. It's not production ready at all.
Stick with terraform if you need to provision non-aws resources. Otherwise, use aws-cdk.
- tonyhb 5y agoI do multiple stacks via changing the state file based off of env: constructor(scope: Construct, name: string, c: StackConfig) { super(scope, name); new S3Backend(this, { bucket: "some-bucket-here", key: c.name("state-env"), region: "" // wherever }); } // ... at the bottom of main new Stack(app, 'something-something-dev', { environment: "dev", name: (i) => `${i}-dev` }); new Stack(app, 'something-something-prod', { environment: "prod", name: (i) => `${i}-prod` }); Then you can use stacks properly.
- cmclaughlin 5y agoSupport for multiple stacks in a single file was added to cdktf recently. I’ve been managing dozens of production stacks in a single repo for a while now and highly recommended it.
- ManWith2Plans 5y agoAnd yet if you try to pass values from one stack to another, it will fail spectacularly.