Superset is configured to use FEATURE_FLAG: DASHBOARD_RBAC to control which roles have access to specific dashboards.
When assets or dashboard is exported, the roles that have access to the dashboards are NOT exported.
How to reproduce the bug
- Enable feature flag DASHBOARD_RBAC and configure a dashboard for a specific role
- Use the REST API export/dashboard or assets/dashboard and download the zip file
- Check the exported dashboard-name.yaml file. The role is not exported
Expected results
Roles are also exported as part of dashboard
Actual results
Roles are not exported
Environment
(please complete the following information):
- browser type and version: Chrome/Mac OS
- superset version: 2.0.0
- python version: 3.8.12
- any feature flags active: DASHBOARD_RBAC
Checklist
Make sure to follow these steps before submitting your issue - thank you!
- [x] I have checked the superset logs for python stacktraces and included it here as text if there are any.
- [x] I have reproduced the issue with at least the latest released version of superset.
- [x] I have checked the issue tracker for the same issue and I haven't found one similar.
Additional context
Add any other context about the problem here.
Comment From: DiogoReisPinto
Facing the same issue
Comment From: rusackas
Is this still an issue in 3.x? I think so, but this needs validation.
Comment From: rusackas
I think @yousoph and @eschutho were taking stock of what is/isn't part of the import/export workflow, so I'll ping them on this. Barring validation and use case, this issue might be closed as stale before too long.
Comment From: rusackas
Assuming this is still the case in 4.0? Tempted to close as stale, but would love to have that validated. I also am not sure the future of DASHBOARD_RBAC or how that may intersect with @dpgaspar 's work around groups.
Comment From: lxrvan
@rusackas hi! I guess it's still the case even in v4.1.2. I couldn't find any mentions of "role"/"roles" in yaml files from .zip exported file.
Comment From: rusackas
If anyone can check in thecurrent version/codebase (i.e. 5.0.0 or on master) that would be appreciated. Otherwise, anyone is welcome to open a PR, but it might eventually be closed as "not planned" or moved to a Discussion thread under the "Ideas" group.