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

[8.15] Permissions for alert suppression in machine learning rules (backport #5819) #5934

Merged
merged 2 commits into from
Oct 16, 2024

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented Oct 16, 2024

Resolves #5492.

Previews

* Update ESS docs: ML rule req for alert suppression

* Update serverless docs, and align with ESS

(cherry picked from commit 632deff)

# Conflicts:
#	docs/serverless/advanced-entity-analytics/ml-requirements.mdx
#	docs/serverless/alerts/alert-suppression.mdx
@mergify mergify bot requested a review from a team as a code owner October 16, 2024 13:32
Copy link
Contributor Author

mergify bot commented Oct 16, 2024

Cherry-pick of 632deff has failed:

On branch mergify/bp/8.15/pr-5819
Your branch is up to date with 'origin/8.15'.

You are currently cherry-picking commit 632deff5.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Changes to be committed:
	modified:   docs/advanced-entity-analytics/ml-req.asciidoc
	modified:   docs/detections/alert-suppression.asciidoc

Unmerged paths:
  (use "git add/rm <file>..." as appropriate to mark resolution)
	deleted by us:   docs/serverless/advanced-entity-analytics/ml-requirements.mdx
	deleted by us:   docs/serverless/alerts/alert-suppression.mdx

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally

Copy link

A documentation preview will be available soon.

Request a new doc build by commenting
  • Rebuild this PR: run docs-build
  • Rebuild this PR and all Elastic docs: run docs-build rebuild

run docs-build is much faster than run docs-build rebuild. A rebuild should only be needed in rare situations.

If your PR continues to fail for an unknown reason, the doc build pipeline may be broken. Elastic employees can check the pipeline status here.

@joepeeples joepeeples enabled auto-merge (squash) October 16, 2024 13:40
@joepeeples
Copy link
Contributor

run docs-build

@joepeeples joepeeples merged commit 0443794 into 8.15 Oct 16, 2024
3 checks passed
@joepeeples joepeeples deleted the mergify/bp/8.15/pr-5819 branch October 16, 2024 14:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant