We just upgraded from 7.5.12 to 10.4.1 - using the legacy alerts for now. Our dashboards/alerts are using the angular plugin.
And we get it, it will be deprecated. But it’s a “bit” (understatement) annoying to have that warning EVERYWHERE.
Is there a way to disable that warning? Maybe a config statement?
Thanks.
you can configure this in your ini:
angularDeprecationUI Display Angular warnings in dashboards and panels Yes
1 Like
I use Docker so I have to use Environment variable
{
"settings": {
"name": "grafana",
"memoryLimit": -1,
"automaticStart": true,
"automaticPortMapping": false,
"exposedPorts": {
"3000": [
"1112",
"127.0.0.1"
]
},
"volumeMapping": [
{
"source": "/docker_storage/grafana",
"destination": "/grafana"
}
],
"environmentVariables": {
"PATH": "/usr/share/grafana/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin",
"GF_PATHS_CONFIG": "/usr/share/grafana/conf/defaults.ini",
"GF_PATHS_DATA": "/grafana/",
"GF_PATHS_HOME": "/usr/share/grafana",
"GF_PATHS_LOGS": "/grafana/logs",
"GF_PATHS_PLUGINS": "/grafana/plugins",
"GF_PATHS_PROVISIONING": "/etc/grafana/provisioning/",
"GF_FEATURE_TOGGLES_PUBLICDASHBOARDS": "true",
"GF_FEATURE_TOGGLES_ENABLE": "publicDashboards",
"GF_AUTH_ANONYMOUS_ENABLED": "true",
"GF_SECURITY_ALLOW_EMBEDDING": "true",
"GF_SERVER_ROOT_URL": "%(protocol)s://%(domain)s:%(http_port)s/grafana/",
"GF_SERVER_SERVE_FROM_SUB_PATH": "true",
"GF_SERVER_DOMAIN": "www.nogodsnomasters.org",
"GF_PLUGIN_REPO": "https://grafana.com/api/plugins",
"GF_LIVE_ALLOWED_ORIGINS": "*",
"GF_LIVE_MAX_CONNECTIONS": "0",
"GF_SERVER_CERT_FILE": "",
"GF_SERVER_CERT_KEY": "",
"GF_SERVER_PROTOCOL": "",
"GF_SECURITY_ANGULAR_SUPPORT_ENABLED": "true",
"GF_FEATURE_TOGGLES_ANGULARDEPRECATIONUI": "false"
}
},
"hasMemoryLimit": true
}
Other users reported the same issue:
grafana:main ← grafana:giuseppe/feature-toggles-env-vars
opened 11:12AM - 08 Jul 24 UTC
<!--
Thank you for sending a pull request! Here are some tips:
1. If this … is your first time, please read our contribution guide at https://github.com/grafana/grafana/blob/main/CONTRIBUTING.md
2. Ensure you include and run the appropriate tests as part of your Pull Request.
3. In a new feature or configuration option, an update to the documentation is necessary. Everything related to the documentation is under the docs folder in the root of the repository.
4. If the Pull Request is a work in progress, make use of GitHub's "Draft PR" feature and mark it as such.
5. If you can not merge your Pull Request due to a merge conflict, Rebase it. This gets it in sync with the main branch.
6. Name your PR as "<FeatureArea>: Describe your change", e.g. Alerting: Prevent race condition. If it's a fix or feature relevant for the changelog describe the user impact in the title. The PR title is used to auto-generate the changelog for issues marked with the "add to changelog" label.
7. If your PR content should be added to the What's New document for the next major or minor release, add the **add to what's new** label to your PR. Note that you should add this label to the main PR that introduces the feature; do not add this label to smaller PRs for the feature.
-->
**What is this feature?**
Allows setting feature toggles via env vars:
```
GF_FEATURE_TOGGLES_<feature_name> = true
```
or
```
GF_FEATURE_TOGGLES_<feature_name> = false
```
This complements the existing way of **enabling** a feature toggle using:
```
GF_FEATURE_TOGGLES_ENABLED = featureOne, featureTwo, featureThree
```
This new way is handy to **disable** a feature toggle enabled by default.
**Why do we need this feature?**
Consistent behaviour of setting ini config values with environment values.
**Who is this feature for?**
Grafana users
**Which issue(s) does this PR fix?**:
<!--
- Automatically closes linked issue when the Pull Request is merged.
Usage: "Fixes #<issue number>", or "Fixes (paste link of issue)"
-->
Fixes #88364
**Special notes for your reviewer:**
Needs docs update as well.
Please check that:
- [x] It works as expected from a user's perspective.
- [x] If this is a pre-GA feature, it is behind a feature toggle.
- [ ] The docs are updated, and if this is a [notable improvement](https://grafana.com/docs/writers-toolkit/writing-guide/contribute-release-notes/#how-to-determine-if-content-belongs-in-a-whats-new-document), it's added to our [What's New](https://grafana.com/docs/writers-toolkit/writing-guide/contribute-release-notes/) doc.
What Grafana version and what operating system are you using?
Grafana OSS v11.0 on Docker
What are you trying to achieve?
Disable the deprecation warning for Angular panel plugin using environment variables. I would like to not use a config file if possible because I have done all the other configuration via environment variables It is not very well documented how to use environment variables to disable feature toggles, only enable new ones, at Configure Grafana | Grafana documentation
…
opened 08:48AM - 28 May 24 UTC
area/plugins
area/frontend
### What happened?
Setting the environment variable
`GF_FEATURE_TOGGLES_ANG… ULARDEPRECATIONUI=False`
does not prevent the Angular deprecation warning popup.
It could be that this the wrong syntax, but it is not well documented how to use environment variables to disable feature toggles.
### What did you expect to happen?
No Angular deprecation warning is displayed when I open a dashboard with a deprecated panel.
### Did this work before?
No, I have not used the GF_FEATURE_TOGGLES env vars before Grafana v11.0, but I use env vars to do all the other Grafana configuration.
### How do we reproduce it?
1. Set env var GF_FEATURE_TOGGLES_ANGULARDEPRECATIONUI=False
2. Start Grafana
3. Create a dashboard with a panel visualization using Angular, for example FlowCharting
4. Observe warning
### Is the bug inside a dashboard panel?
No
### Environment (with versions)?
Grafana: 11.0
Docker image: grafana/grafana-oss:11.0.0
### Grafana platform?
Docker
### Datasource(s)?
_No response_
```[tasklist]
### Tasks
```
I’m stuck in a dead end. Can’t upgrade the deprecated plugin and can’t disable the annoying warning.
