Daniel Schmidt

Yeah unfortunately it's expected. It's a bug we have been planning to fix by moving to Terraform directly for all TFC/TFE related interaction, but we haven't finalised the fix yet

We should check if using symbols solves this problem, e.g. like we do in https://github.com/hashicorp/terraform-cdk/blob/main/packages/cdktf/lib/terraform-stack.ts#L43-L45

@jsteinich I think it's fine to delete it. We are even thinking in the direction of generating it from the provider bindings used: https://github.com/hashicorp/terraform-cdk/issues/2200

I'm picking up work on the overarching `cdktf provider update` command (#1745), just so you know :)

While we seem to have answered the question I'd like to keep this issue open and add a proper warning / error if someone passes a stack into synthScope.

This is because your construct contains a stack. A stack does not synthesize into JSON like a construct would, but it writes a file to disk with it's childrens JSON...

We can use https://pypi.org/project/pypi-cleanup/ to cleanup old releases, will do this manually for the package in question for now and we can come back to it later and automate it...

- We should reduce the update interval to once a day down from six times a day - We should request a higher threshold: https://github.com/pypa/pypi-support/issues/new?assignees=&labels=limit+request&template=limit-request-project.yml&title=Project+Limit+Request%3A+PROJECT_NAME+-+00+GB

I cleared the 0.1.x releases, that should give us some room again

Yes @brad-lucas it's the best place to bring this up, I'm clearing the releases again now. From this point on pypi only hosts this prebuilt provider from cdktf version 0.8...