Joey Orlando 673d2e9595 feat: persist is_grafana_irm_enabled from backend plugin sync data (#5171) ... # What this PR does Will start persisting the `organization.is_grafana_irm_enabled` flag from the backend plugin's sync data that is sent to the oncall backend. The implications of this are that when `is_grafana_irm_enabled` is set to True, we will: - start using `grafana-irm-app` prefixed RBAC permissions (RBAC permissions for `grafana-irm-app`, as well as `grafana-oncall-app`, are already being synced to the OnCall backend since https://github.com/grafana/irm/pull/200 was merged/deployed) - start building UI URLs w/ `grafana-irm-app` instead of `grafana-oncall-app` ## Which issue(s) this PR closes Closes https://github.com/grafana/irm/issues/242 ## Checklist - [x] Unit, integration, and e2e (if applicable) tests updated - [x] Documentation added (or `pr:no public docs` PR label added if not required) - [x] Added the relevant release notes label (see labels prefixed w/ `release:`). These labels dictate how your PR will show up in the autogenerated release notes.		2024-10-11 14:57:59 -04:00
..
__init__.py	Add basic organization moved exception handling and middleware	2022-10-20 15:04:58 -06:00
organization.py	feat: persist is_grafana_irm_enabled from backend plugin sync data (#5171)	2024-10-11 14:57:59 -04:00
region.py	apps.get_model -> import (#2619)	2023-07-25 09:43:23 +00:00
team.py	Rework organization sync and grafana plugin engine backend (#4756)	2024-07-31 16:12:56 +00:00
user.py	feat: update RBAC permissioning to support grafana-irm-app (#5149)	2024-10-10 19:02:21 +00:00