-
Notifications
You must be signed in to change notification settings - Fork 297
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Connector API for Grafana to automatically connect Grafana to the existing OnCall instance #122
Comments
We added this task to the core team's backlog. |
I believe this could be done with a secret and the plugins sidecar already. For example: apiVersion: v1
kind: Secret
metadata:
name: oncall-plugin
namespace: oncall
labels:
grafana_plugin: ""
type: Opaque
stringData:
oncall-plugin.yaml: |
apiVersion: 1
apps:
- type: grafana-oncall-app
name: grafana-oncall-app
disabled: false
jsonData:
grafanaUrl: https://grafana.example.com
onCallApiUrl: https://oncall.example.com
secureJsonData:
onCallInvitationToken: xxxx While this does configure the plugin, I'm getting an error about the token being invalid ( |
@davidspek There is the limitation in current frontend, so we cannot provision the plugin with the token. It will be fixed by in this issue #452 and the auto-provisioning will become possible |
#452 is closed so this one is unblocked :) |
This issue has been automatically marked as stale because it has not had activity in the last 120 days. |
Are there any updates or workaround on this? I believe #3761 refers to somewhat the same issue. |
According to the changelog, this should already be possible: https://github.com/grafana/oncall/blob/dev/CHANGELOG.md#v113-2022-11-22
But unfortunately this doesn't work. The code in question: oncall/grafana-plugin/src/utils/consts.ts Lines 38 to 50 in 3566de3
Contrary to the comment on Edit: Reading the git history, this probably (but I'm not entirely sure) worked fine until commit 92fa509 from PR: Anyway, I would prefer to have working plugin provisioning via |
Recently we made some changes to the way Grafana OnCall is initialized. Use 1.9.22, there were quite a few changes along the way from 1.9.0-1.9.22 to get things working.
Grafana OnCall should now be ready to use. |
It would be great to automatically connect on-premise Grafana instance during upgrade (via helm etc) to the existing OnCall instance via custom env variables, or config in grafana.ini and config in oncall helm chart.
The text was updated successfully, but these errors were encountered: