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.9] Adds kibana namespace requirement to CNVM and CSPM (backport #5154) #5178

Closed
wants to merge 1 commit into from

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented May 7, 2024

Fixes #5107

A small change on several pages. I reviewed the previews already.


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

* Updates requirements section for CNVM and CSPM

* minor updates - adds attribute

(cherry picked from commit 5df1b3a)

# Conflicts:
#	docs/cloud-native-security/cspm-get-started-azure.asciidoc
#	docs/cloud-native-security/cspm-get-started-gcp.asciidoc
#	docs/cloud-native-security/cspm-get-started.asciidoc
#	docs/cloud-native-security/cspm.asciidoc
Copy link
Contributor Author

mergify bot commented May 7, 2024

Cherry-pick of 5df1b3a has failed:

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

You are currently cherry-picking commit 5df1b3a2.
  (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-get-started.asciidoc
	modified:   docs/cloud-native-security/vuln-management-overview.asciidoc

Unmerged paths:
  (use "git add/rm <file>..." as appropriate to mark resolution)
	deleted by us:   docs/cloud-native-security/cspm-get-started-azure.asciidoc
	deleted by us:   docs/cloud-native-security/cspm-get-started-gcp.asciidoc
	both modified:   docs/cloud-native-security/cspm-get-started.asciidoc
	both modified:   docs/cloud-native-security/cspm.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 May 7, 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 benironside closed this May 7, 2024
@mergify mergify bot deleted the mergify/bp/8.9/pr-5154 branch May 7, 2024 16:08
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