Daniel Schmidt

No, you can plan the stack housing the value, apply it and the plan the stack using the value. If you plan the stack using the value first your plan...

I'd rather have a second type since I want to expose the direct sensor values. But I can see that this normalized form makes more sense

Fixed in #1955, now it should behave exactly the same as with Terraform CLI (since we are using Terraform CLI under the hood)

@maxdeviant I added an author field, the `theme_importer` did not emit it unfortunately :D

Oh I was not aware that a project without a cdktf.json is valid, I added this check with the intend to keep people from using cdktf outside of a cdk...

I think we would accept contributions 👍

A PR would be cool, I encounter the same problem

AFAIK Zipkin only provides one interface for span annotations, we need to use that I would guess. We currently implement [log](https://github.com/DanielMSchmidt/zipkin-javascript-opentracing/blob/master/src/index.js#L124-L133), so we could write it like this: ```js addTags(tags)...

Could you try `import * as ZipkinOpentracing from 'zipkin-javascript-opentracing'`? It's just a lucky guess

But that is correct, we have no typescript definitions so far. Would be super awesome to get some, would love to see a PR :)