Separate workflow configuration and content (deploy-as-a-code)

[maxlapshin]

What would you like to see!

I have following process:

1. We develop on-premises software and it is a first layer of configuration. Here we must link together all parts of software, like mutual configuration of plugin and grafana. This must live in git in reviewable form.

2. Then we configure it on customer site, where we put all escalation chains, link with calendars, etc. This configuration will change only if business process changes and should be kept in git, where live all other project configuration. However, it may be a database dump

3. Customer starts working and periodically backup database, but content here is less important than configuration.

So I have questions:

1. Am I correct, that there is no simple way to deploy oncall with the rest of cluster in a yaml fashion via grafana provision mechanism?
2. Am I alone with such wishes? Maybe somebody else is moving there and we can join our efforts to enhance this software?
3. Does this approach matches with roadmap of oncall team? I suppose that if you develop cloud service, then spending time on deploying from scratch with yaml configuration maybe not in your focus.

Product Area

Alert Flow & Configuration

Anything else to add?

No response

[github-actions]

The current version of Grafana OnCall, at the time this issue was opened, is v1.13.5. If your issue pertains to an older version of Grafana OnCall, please be sure to list it in the PR description. Thank you 😄!