-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
[DOCS] Allow users authenticated with API keys to manage alerting rules #158428
Merged
Conversation
This file contains 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
lcawl
added
Feature:Alerting
release_note:skip
Skip the PR/issue when compiling release notes
Team:ResponseOps
Label for the ResponseOps team (formerly the Cases and Alerting teams)
docs
backport:prev-minor
Backport to (8.x) the previous minor version (i.e. one version back from main)
v8.9.0
v8.8.1
labels
May 24, 2023
Documentation preview: |
🤖 GitHub commentsExpand to view the GitHub comments
Just comment with:
|
lcawl
commented
May 24, 2023
docs/user/alerting/troubleshooting/alerting-common-issues.asciidoc
Outdated
Show resolved
Hide resolved
Pinging @elastic/response-ops (Team:ResponseOps) |
ymao1
approved these changes
May 25, 2023
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
kibanamachine
pushed a commit
to kibanamachine/kibana
that referenced
this pull request
May 25, 2023
…es (elastic#158428) (cherry picked from commit 4cf817a)
💚 All backports created successfully
Note: Successful backport PRs will be merged automatically after passing CI. Questions ?Please refer to the Backport tool documentation |
kibanamachine
added a commit
that referenced
this pull request
May 25, 2023
…ng rules (#158428) (#158497) # Backport This will backport the following commits from `main` to `8.8`: - [[DOCS] Allow users authenticated with API keys to manage alerting rules (#158428)](#158428) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Lisa Cawley","email":"[email protected]"},"sourceCommit":{"committedDate":"2023-05-25T17:32:11Z","message":"[DOCS] Allow users authenticated with API keys to manage alerting rules (#158428)","sha":"4cf817a1abb3ddd657c7c11d75c5bd7f9e8aed27","branchLabelMapping":{"^v8.9.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:Alerting","release_note:skip","Team:ResponseOps","docs","backport:prev-minor","v8.9.0","v8.8.1"],"number":158428,"url":"https://github.com/elastic/kibana/pull/158428","mergeCommit":{"message":"[DOCS] Allow users authenticated with API keys to manage alerting rules (#158428)","sha":"4cf817a1abb3ddd657c7c11d75c5bd7f9e8aed27"}},"sourceBranch":"main","suggestedTargetBranches":["8.8"],"targetPullRequestStates":[{"branch":"main","label":"v8.9.0","labelRegex":"^v8.9.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/158428","number":158428,"mergeCommit":{"message":"[DOCS] Allow users authenticated with API keys to manage alerting rules (#158428)","sha":"4cf817a1abb3ddd657c7c11d75c5bd7f9e8aed27"}},{"branch":"8.8","label":"v8.8.1","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Lisa Cawley <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
backport:prev-minor
Backport to (8.x) the previous minor version (i.e. one version back from main)
docs
Feature:Alerting
release_note:skip
Skip the PR/issue when compiling release notes
Team:ResponseOps
Label for the ResponseOps team (formerly the Cases and Alerting teams)
v8.8.0
v8.8.1
v8.9.0
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.
Summary
Fixes #154580