[CT-3527] [implementation] extend access and groups to exposures & source #9339
Open
1 of 5 tasks
Labels
enhancement
New feature or request
model_groups_access
Issues related to groups
multi_project
user docs
[docs.getdbt.com] Needs better documentation
Housekeeping
Short description
From the discussion here...
We should extend
group
configurations to all resource types. The current outstanding ones aresources
andexposures
:We should also enable
sources
to configureaccess
toprivate
orprotected
(default). We should not allow folks to setaccess
topublic
forsources
.Acceptance criteria
group
config for an exposuregroup
config for a sourceaccess
toprivate
orprotected
(default) for a sourceaccess
for an exposure (they are inherently public)As described here, referencing a resource outside of its supported access should raise an error (but otherwise should not).
Impact to Other Teams
none
Will backports be required?
none
Context
Notes from technical refinement:
The text was updated successfully, but these errors were encountered: