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.8] New page about allowlisting Elastic Endpoint in 3rd-party AV software (backport #4439) #4509

Merged
merged 1 commit into from
Dec 21, 2023

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented Dec 21, 2023

This is an automatic backport of pull request #4439 done by Mergify.


Mergify commands and options

More conditions and actions can be found in the documentation.

You can also trigger Mergify actions by commenting on this pull request:

  • @Mergifyio refresh will re-evaluate the rules
  • @Mergifyio rebase will rebase this PR on its base branch
  • @Mergifyio update will merge the base branch into this PR
  • @Mergifyio backport <destination> will backport this PR on <destination> branch

Additionally, on Mergify dashboard you can:

  • look at your merge queues
  • generate the Mergify configuration with the config editor.

Finally, you can contact us on https://mergify.com

…#4439)

* Adds new page about allowlisting Elastic Endpoint

* Update docs/management/admin/allowlist-endpoint-3rd-party-av.asciidoc

Co-authored-by: Daniel Ferullo <56368752+ferullo@users.noreply.github.com>

* Update docs/management/admin/allowlist-endpoint-3rd-party-av.asciidoc

Co-authored-by: Daniel Ferullo <56368752+ferullo@users.noreply.github.com>

* incorporates feedback

* incorporates Gabriel Landau's feedback

---------

Co-authored-by: Daniel Ferullo <56368752+ferullo@users.noreply.github.com>
(cherry picked from commit 08a7c08)
Copy link

A documentation preview will be available soon.

Help us out by validating the Buildkite preview and reporting issues here.
Please also be sure to double check all images to ensure they are correct in the preview.

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.

@benironside benironside merged commit 6df8791 into 8.8 Dec 21, 2023
4 checks passed
@mergify mergify bot deleted the mergify/bp/8.8/pr-4439 branch December 21, 2023 18:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant