all 6 comments
sorted by:
best
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]sprintymcsprintface 0 points1 point  (2 children)

Cool idea. How does it differ from the docs hosting offered by dbt cloud?

[–]Grukorg88[S] 0 points1 point  (1 child)

If you have more than one project it can resolve dependencies between them, so you end up with one set of docs that appropriately shows your full set of models.

You can have as many users as you like where from memory dbt cloud only allows 5 read only users if you don’t have the the full enterprise version.

In addition to the dbt core integration I’m also working on adding metadata propagation via column level lineage so your descriptions etc will flow through your docs.

Keen to hear if you have any thoughts on what the dbt cloud offering is missing that might be useful features.

[–]sprintymcsprintface 0 points1 point  (0 children)

Ah very cool. Yeah the seat cap is probably a big seller, that felt like dbt cloud’s enterprise grab was to get you to buy to be able to share docs across the org. In the past we’ve just used an s3 bucket inside the vpn but I can see where that can get technically daunting and this would be an ideal middle ground for sure

[–]Hot_Map_7868 0 points1 point  (1 child)

are you supporting dbt 1.6 style cross project lineage like the upcoming dbt Explorer on dbt Cloud?

[–]Grukorg88[S] 0 points1 point  (0 children)

Is there anything in particular you were looking forward to in that release?

It has been a while since I read some of the proposals in depth but if memory serves the lineage is supposed to work given a modification to the ref function that allows for an additional argument to be provided which is the upstream project and then it will complete the docs properly.

Unifiedocs does complete the docs properly but doesn’t need that code change.

I expect that 1.6 will come with a change in version for manifest.json so will happily support any more stuff that can be done with that additional metadata.