mirror of https://github.com/apache/superset.git
chore(docs): feature flags setting is misleading in docs (#20622)
This commit is contained in:
parent
c29261b63d
commit
0a316a8ed3
|
@ -183,7 +183,7 @@ Access to dashboards is managed via owners (users that have edit permissions to
|
||||||
Non-owner users access can be managed two different ways:
|
Non-owner users access can be managed two different ways:
|
||||||
|
|
||||||
1. Dataset permissions - if you add to the relevant role permissions to datasets it automatically grants implicit access to all dashboards that uses those permitted datasets
|
1. Dataset permissions - if you add to the relevant role permissions to datasets it automatically grants implicit access to all dashboards that uses those permitted datasets
|
||||||
2. Dashboard roles - if you enable **DASHBOARD_RBAC** feature flag then you be able to manage which roles can access the dashboard
|
2. Dashboard roles - if you enable **DASHBOARD_RBAC** [feature flag](https://superset.apache.org/docs/installation/configuring-superset#feature-flags) then you be able to manage which roles can access the dashboard
|
||||||
- Having dashboard access implicitly grants read access to the associated datasets, therefore
|
- Having dashboard access implicitly grants read access to the associated datasets, therefore
|
||||||
all charts will load their data even if feature flag is turned on and no roles assigned
|
all charts will load their data even if feature flag is turned on and no roles assigned
|
||||||
to roles the access will fallback to **Dataset permissions**
|
to roles the access will fallback to **Dataset permissions**
|
||||||
|
|
|
@ -22,7 +22,7 @@ Alerts and reports are disabled by default. To turn them on, you need to do some
|
||||||
|
|
||||||
##### In your `superset_config.py`
|
##### In your `superset_config.py`
|
||||||
|
|
||||||
- `"ALERT_REPORTS"` feature flag must be turned to True.
|
- `"ALERT_REPORTS"` [feature flag](https://superset.apache.org/docs/installation/configuring-superset#feature-flags) must be turned to True.
|
||||||
- `CELERYBEAT_SCHEDULE` in CeleryConfig must contain schedule for `reports.scheduler`.
|
- `CELERYBEAT_SCHEDULE` in CeleryConfig must contain schedule for `reports.scheduler`.
|
||||||
- At least one of those must be configured, depending on what you want to use:
|
- At least one of those must be configured, depending on what you want to use:
|
||||||
- emails: `SMTP_*` settings
|
- emails: `SMTP_*` settings
|
||||||
|
|
|
@ -44,7 +44,7 @@ defined in `DATA_CACHE_CONFIG`.
|
||||||
|
|
||||||
### Caching Thumbnails
|
### Caching Thumbnails
|
||||||
|
|
||||||
This is an optional feature that can be turned on by activating it’s feature flag on config:
|
This is an optional feature that can be turned on by activating it’s [feature flag](https://superset.apache.org/docs/installation/configuring-superset#feature-flags) on config:
|
||||||
|
|
||||||
```
|
```
|
||||||
FEATURE_FLAGS = {
|
FEATURE_FLAGS = {
|
||||||
|
|
|
@ -10,7 +10,7 @@ version: 1
|
||||||
### Jinja Templates
|
### Jinja Templates
|
||||||
|
|
||||||
SQL Lab and Explore supports [Jinja templating](https://jinja.palletsprojects.com/en/2.11.x/) in queries.
|
SQL Lab and Explore supports [Jinja templating](https://jinja.palletsprojects.com/en/2.11.x/) in queries.
|
||||||
To enable templating, the `ENABLE_TEMPLATE_PROCESSING` feature flag needs to be enabled in
|
To enable templating, the `ENABLE_TEMPLATE_PROCESSING` [feature flag](https://superset.apache.org/docs/installation/configuring-superset#feature-flags) needs to be enabled in
|
||||||
`superset_config.py`. When templating is enabled, python code can be embedded in virtual datasets and
|
`superset_config.py`. When templating is enabled, python code can be embedded in virtual datasets and
|
||||||
in Custom SQL in the filter and metric controls in Explore. By default, the following variables are
|
in Custom SQL in the filter and metric controls in Explore. By default, the following variables are
|
||||||
made available in the Jinja context:
|
made available in the Jinja context:
|
||||||
|
|
Loading…
Reference in New Issue