Open joeyorlando opened 3 months ago
The current version of Grafana OnCall, at the time this issue was opened, is v1.7.1. If your issue pertains to an older version of Grafana OnCall, please be sure to list it in the PR description. Thank you :smile:!
See this Slack thread for some more discussion/ideas
One thing to note is that the Env Variables page can give useful info when things are not configured properly. We should probably surface these warnings somewhere (ex. logging on startup or some other endpoint)
@joeyorlando WDYT about keeping the page, but use it only for validation without ability to edit things?
@Konstantinov-Innokentii I think that could make sense 👍 (@mderynck had a similar idea). We'd probably need some design input from @raphael-batte here.
What would you like to see!
I've combed through the issues/bug reports here in the repo and it feels like this page leads to more confusion than it is helpful. This isn't an exhaustive list but here are a few bug reports I came across:
In short, for OSS deployments of Grafana OnCall, we should have only one way of configuring things, via environment variables.
Deliverables
NOTES
We may want to consider releasing this change as a part of v2.0.0 as it's possible this would be a breaking change (ex. user was using live settings, would need to manually migrate their live settings values to environment variables in their deployment).
Product Area
Alert Flow & Configuration
Anything else to add?
No response