Vardan Torosyan

@grafana/plugins-platform-backend would appreciate if someone from your end can take a look at this PR, as it seems that it would make sense to get this merged for 9.1. Thanks!

## Context The issue has been introduced with Grafana 9.0 release and the root cause is in the underlying implementation of data source permissions with RBAC (role-based access control). When...

FYI, as a temporary workaround one can hardcode the following which will have no impact ``` permissions { permission = "Query" } ```

One temporary idea for the fix could be updating terraform provider to filter out the default `Query` returned by Grafana and ignore it when comparing with the state. @kalleep @IevaVasiljeva...

A quick update: - Since now we have Grafana service accounts, as well as upcoming [terraform resource](https://github.com/grafana/terraform-provider-grafana/pull/524) for it, to fully support RBAC we would also need to make it...

@NickAdolf thanks for the feedback. Unfortunately I can't unfortunately any exact ETA at the moment, but can share for sure that we are going to start working on this around...

Reopening as the terraform PR is still open (this was automatically marked as closed)

@eleijonmarck I think the milestone is wrong for this. Could you please verify and change it to 9.3 ?

I am still a bit hesitant to remove the POST endpoint with appropriate announcement with a good notice. What about having a blog post sharing timeline for full sunsetting of...

@hbjydev thanks for the comment! Indeed the scenario you mentioned is one of the Grafana Teams limitations. We have that in mind and it is one of the first priorities...