Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: disable accessControlOnCall for Grafana 11.3 #5245

Merged
merged 4 commits into from
Nov 12, 2024

Conversation

brojd
Copy link
Contributor

@brojd brojd commented Nov 8, 2024

What this PR does

Disable accessControlOnCall for Grafana 11.3

Checklist

  • Unit, integration, and e2e (if applicable) tests updated
  • Documentation added (or pr:no public docs PR label added if not required)
  • 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.

@brojd brojd added the pr:no public docs Added to a PR that does not require public documentation updates label Nov 8, 2024
@brojd brojd requested a review from a team as a code owner November 8, 2024 06:49
@brojd brojd added the release:patch PR will be added to "Other Changes" section of release notes label Nov 8, 2024
@bpedersen2
Copy link

It would be nice to see in the commit message where it is disabled (in the tests only).
related to #5100

@brojd brojd added this pull request to the merge queue Nov 12, 2024
Merged via the queue into dev with commit df6bb69 Nov 12, 2024
25 checks passed
@brojd brojd deleted the brojd/adjust-to-Grafana-11.3 branch November 12, 2024 16:15
github-merge-queue bot pushed a commit that referenced this pull request Nov 14, 2024
…5255)

# What this PR does

Disable accessControlOnCall for Grafana 11.3 in docker compose
Similar to #5245

## Checklist

- [ ] 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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
pr:no public docs Added to a PR that does not require public documentation updates release:patch PR will be added to "Other Changes" section of release notes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants