Daniel Schmidt

This looks like the question is answered, closing it for now :)

I think we can just increase the requirement to Python 3.7 on our side

You can use `apply` instead of `deploy`, but we need to keep `deploy` to stay compliant with the AWS cdk

They don't have to be in sync, but there are a lot of folks coming from the AWS CDK so we want to make their transitions as easy as possible.

I'm sorry that happened to you! I definitely agree, a lot of folks come from Terraform, even more than from the AWS CDK would be my guess. That is why...

You would need to take terraform functions in this case. It should look sth like this: `Fn.lookup(Fn.lookup(Fn.lookup(Fn.element(webappService.status.fqn, 0), "load_balancer"), "ingress"), "ip")`

Hey, great point! We have no good way of inferring the outputs (@ansgarm brought up an idea with evaluating the TF like `terraform validate` does and using that type information...

We could use the parsing of the variable names as well for convert: #1891

In my vision higher level constructs (and basic constructs like Asset) would use this new construct, I think it would rarely be used at the top-level. The advantage of using...

> If I understand this correctly, this aims mainly at: > > 1. Asset like constructs > 2. Potential other input files, perhaps something like a JSON config file or...