Replies: 4 comments
-
Hi @ishk0, thanks for starting the discussion. My first guess is that the datasource created with Ansible is different from the one created manually. Have you made sure they are the same? The best thing to do is to use an API request to output the datasources and compare them. |
Beta Was this translation helpful? Give feedback.
-
Here's a demonstration of the problem. I don't see any difference between these datasources, even though one of them was created by an Ansible playbook and the other one manually. |
Beta Was this translation helpful? Give feedback.
-
Update on the situation: I noticed that if I change the Host URL of the Ansible-created datasource to an incorrect value and then revert it back to the correct one, the Editor also gains access to "SELECT". |
Beta Was this translation helpful? Give feedback.
-
Thanks for the further information on the problem. I would be interested in comparing the two data sources using the JSON through the Grafana-API, not through the web interface. |
Beta Was this translation helpful? Give feedback.
-
Hello,
I am using:
My community.grafana.grafana_datasource module configuration:
I noticed that a Grafana user with the Editor role cannot perform a SELECT operation on this Alpha datasource. However, if I manually create an identical Alpha-man datasource, the Editor role has SELECT access.
If I grant the admin role to the user, SELECT works for both datasources.
Could you please help me understand how to configure the role correctly? Thank you!
Beta Was this translation helpful? Give feedback.
All reactions