Relevant - confirming that schema perms are managed as part of
`dataset_after_update` and oddly at first sight, not on
`dataset_after_insert`, unless I'm missing anything, like after_update
called after insert somewhere?
I haven't looked at the code, but as a workaround, creating one dataset on
that schema may create the schema-level permission. Also I think
schema-level permissions don't apply to SQL Lab (not sure).
Thinking about solutions, Superset could use some sort of [optional]
database agent that would
Hello Team,
I hope to find you in good health.
I have been working on an implementation where we are providing permissions to
different schemas through user roles.
We encountered a scenario as described below:
1. A new schema was created in Redshift database. We have an existing
database
