DEV-46158 Allow Editors to Manage Alerting Provisioning #42
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
run-test |
ohadza
approved these changes
Sep 12, 2024
yasmin-tr
deleted the
DEV-46158-Allow-editors-to-manage-alerting-provisioning
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What is this feature?
In grafana 10 we have RBAC (role-based access control) enabled
For some reason the alerting provisioning apis has permissions for Admins only.
Since in logz for all the users are Editor in their organization (and only the system admin has Admin role), we need to fix so that the Editor role will also have write permissions for alerts api, otherwise they are unable to use provisioning API.
Why do we need this feature?
We want users to be able to use the provisioning API so they need the proper access with their existing roles.