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] [CNVM] Adds notes about CNVM architecture support (backport #5340) #5546

Closed
wants to merge 1 commit into from

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented Jul 9, 2024

Fixes #5304. Adds a note with a previously undocumented requirement for the CNVM integration.

Previews: Get started with CNVM
CNVM FAQ


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

* Adds notes about CNVM architecture support

* Update docs/cloud-native-security/vuln-management-faq.asciidoc

* Update docs/cloud-native-security/vuln-management-get-started.asciidoc

(cherry picked from commit d1cd713)

# Conflicts:
#	docs/cloud-native-security/vuln-management-get-started.asciidoc
Copy link
Contributor Author

mergify bot commented Jul 9, 2024

Cherry-pick of d1cd713 has failed:

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

You are currently cherry-picking commit d1cd713b.
  (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/cloud-native-security/vuln-management-faq.asciidoc

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   docs/cloud-native-security/vuln-management-get-started.asciidoc

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

github-actions bot commented Jul 9, 2024

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.

@benironside
Copy link
Contributor

will fix in a separate PR

@benironside benironside closed this Jul 9, 2024
@mergify mergify bot deleted the mergify/bp/8.8/pr-5340 branch July 9, 2024 19:58
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