Closed Hronom closed 1 month ago
Seems like deletion of orgId: "1"
in configs helps.
For example I deleted in dashboard
and it start work.
Old:
apiVersion: oss.grafana.crossplane.io/v1alpha1
kind: Dashboard
metadata:
name: ...
spec:
forProvider:
orgId: "1"
folder: ...
configJson: ...
overwrite: true
providerConfigRef:
name: ...
New:
apiVersion: oss.grafana.crossplane.io/v1alpha1
kind: Dashboard
metadata:
name: ...
spec:
forProvider:
folder: ...
configJson: ...
overwrite: true
providerConfigRef:
name: ...
That is expected. You can only set the orgID of a resource when using basic auth. The reason for that is that the Grafana API will silently ignore the org ID when a SA token is used, leading to confusion when users try to deploy resources in another org
Thanks, this helps
Hello, is there was some recent changes in grafana cloud? We start getting error:
Version: v0.14.1 Same also in v0.16.1