You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
We deploy the Grafana Operator to OpenShift. Right now it is only for us as an infrastructure team. But, looking further down the line, we can imagine to grant access to our Grafana or provide it "as service" for different OpenShift clusters of teams and tenants.
To regulate the access to specific teams or tenants the Organization (Orgs) and Teams feature of Grafana would be quite helpful.
Describe the solution you'd like
My "happy-go-lucky" solution would be a CRD for either Teams and Orgs, that are used by the operator to generate both. As per documentation of Grafana the go-to way would be to use the /api/orgs/ endpoint and generate these via API and the admin account.
Describe alternatives you've considered
Right now we are considering to run a Job triggered by the "Post-Sync" hook of ArgoCD and create the Orgs via API-calls ourself.
We try to remove all manual input of us after cluster creation, therefore manual "administration" is a no-go
If this is something "accepted" by the community I would like to implement this feature, since it would greatly benefit us.
The text was updated successfully, but these errors were encountered:
Duplicate of: #408
As written in 408, it's nothing that we are currently prioritizing but if you feel like taking a stab at it we love to get a PR.
As a workaround we could also use your Post-Sync hooks in ArgoCD as documentation, I think some users would find this as a good start as well :)
Is your feature request related to a problem? Please describe.
We deploy the Grafana Operator to OpenShift. Right now it is only for us as an infrastructure team. But, looking further down the line, we can imagine to grant access to our Grafana or provide it "as service" for different OpenShift clusters of teams and tenants.
To regulate the access to specific teams or tenants the Organization (Orgs) and Teams feature of Grafana would be quite helpful.
Describe the solution you'd like
My "happy-go-lucky" solution would be a CRD for either Teams and Orgs, that are used by the operator to generate both. As per documentation of Grafana the go-to way would be to use the /api/orgs/ endpoint and generate these via API and the admin account.
Describe alternatives you've considered
Right now we are considering to run a Job triggered by the "Post-Sync" hook of ArgoCD and create the Orgs via API-calls ourself.
We try to remove all manual input of us after cluster creation, therefore manual "administration" is a no-go
If this is something "accepted" by the community I would like to implement this feature, since it would greatly benefit us.
The text was updated successfully, but these errors were encountered: