Skip to content

Conversation

@mergify
Copy link
Contributor

@mergify mergify bot commented Nov 26, 2024

Fixes #6044 — creates a troubleshooting page for the new agentless integration.

Preview: Agentless integrations FAQESS, Serverless


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

* create agentless troubleshooting steps

* incorporates Omolola's comment

* incorporates Nastasha's review and adds serverless version

* fixes typo

* fix fleet refs

* minor edit

* incorporates Janeen's review and updates fleet refs in ESS version

(cherry picked from commit db188fa)

# Conflicts:
#	docs/serverless/index.asciidoc
@mergify mergify bot added the backport label Nov 26, 2024
@mergify mergify bot requested a review from a team as a code owner November 26, 2024 22:25
@mergify mergify bot added the conflicts label Nov 26, 2024
@mergify
Copy link
Contributor Author

mergify bot commented Nov 26, 2024

Cherry-pick of db188fa has failed:

On branch mergify/bp/8.x/pr-6184
Your branch is up to date with 'origin/8.x'.

You are currently cherry-picking commit db188fa3.
  (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:
	new file:   docs/getting-started/agentless-troubleshooting.asciidoc
	modified:   docs/getting-started/index.asciidoc
	new file:   docs/serverless/ingest/agentless-troubleshooting.asciidoc

Unmerged paths:
  (use "git add/rm <file>..." as appropriate to mark resolution)
	deleted by us:   docs/serverless/index.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

@github-actions
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.

@benironside
Copy link
Contributor

run docs-build

@benironside benironside merged commit 10a2b40 into 8.x Nov 26, 2024
3 checks passed
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