Sergey Polzunov

moved to milestone 0.5 to wait for https://github.com/blackstork-io/fabric/issues/159 as it is an enabler for this issue

an alternative namespacing schema that does not break [HCL identifier constraint](https://developer.hashicorp.com/terraform/language/syntax/configuration#identifiers) is to use `--` as a separator: ```hcl document "my-doc" { section ref { base = fabric_templates--section.ctid_executive_summary } }...

@dobarx oh, that's neat! I like `import..` a lot, awesome idea! It is clear that it is an import while the name is nicely namespaced. Let's go with it!

One thing that occurred to me: We talked about adding a manifest-like to the plugins. Another argument and use case for it, in the context of template distribution in the...

It is pretty close to the dynamic block concept (I'm still working on the issue for that), indeed! We need to figure out an unobstructed syntax here -- it would...

with https://github.com/blackstork-io/fabric/issues/142 in mind, I think this issue still stands -- dynamic blocks are not well suitable for not-null checks

that's neat, it's declarative and provides more options. To reduce the nest-iness, maybe it can be a content block with some flag, like ```hcl content table { query = "..."...

still not great :) it's confusing -- is `empty_result` / `when_empty` about the parent block or the nested block?

oh, that's lovely. ```hcl content table { query = "..." ... on_empty content text { value = "Empty data!" } } content table { query = "..." ... on_empty content...

moving this to draft since https://github.com/blackstork-io/fabric/issues/142 already can provide the functionality, even though in a bit wordy way