Jon Steinich

> I understood issue. I am interested to work on it but not getting where to start. Will anyone like to help me ? @jsteinich @ansgarm @skorfmann Are you in...

@digitalsanctum I think what you're after is covered by #16. This is going farther and converting a terraform module into a construct tree. Writing in code would look very similar...

> Could we add in the meantime a `Testing.toHaveResourceWithProperties` method to test at least the input of a module? Unfortunately modules aren't compatible with how the tests work as the...

> But I have the input of the module in the Synth output. That’s better than nothing. Ah, I'd probably opt for having a `Testing.toHaveModuleWithProperties` to clarify that it is...

@aayushharwani-aidash There are probably several levels to this. I don't think there's been much demand for this, so we'd probably just want to start with some of the basics. Levels...

@DanielMSchmidt do you have an example of a case that you'd like to change? I can see a case in code, but my previous provider snapshot didn't actually have any...

There are a couple motivations for local modules to be treated as assets: - When invoking Terraform Cloud from cdktf, any modules used need to be accessible. Packing as assets...

> > Is it possible to just trigger cdktf synth as part of the VCS workflow? Not having to run cdktf synth locally is a nicer flow from my experience....

I'm a bit torn on whether an update to disable the auto upgrade is needed. From a developer perspective it seems unnecessary as you already went through the effort to...

I'm leaning more towards providing an option to disable the automatic lock file update. I think it makes sense as a value in `cdktf.json` rather than a cli option for...