Closed mmmatthew closed 2 years ago
Is what we already have not sufficient for this? https://github.com/gouline/dbt-metabase#visibility-types
@gouline
What we have is field level visibility setting adjustment.
What is available through Metabase and what he is suggesting is table level visibility adjustment. Which makes sense given how dbt proliferates tables/views as models which might not need to be seen or so easily exposed. The implementation would likely look very similar to what you have already, just scoped to the table endpoint.
Ahh, got it. Once 0.8.0 is dealt with, we can look at implementing this.
@gouline Is this still being worked on or in the plans?
Ask @mmmatthew, he's working on #71
Sorry, I don't have plans to continue this in the near future. Someone else is welcome to pick it up.
It would be useful to automatically hide/show models in Metabase. The metabase API endpoint
PUT /api/table/:id
accepts avisibility_type
value that may be nil, or if non-nil, value must be one of:cruft
,hidden
,technical
. Can we allow theto be defined on models?