Skip to content

[8.14] [ESS] BYO LLM guide (backport #5530)#5533

Merged
benironside merged 1 commit into
8.14from
mergify/bp/8.14/pr-5530
Jul 9, 2024
Merged

[8.14] [ESS] BYO LLM guide (backport #5530)#5533
benironside merged 1 commit into
8.14from
mergify/bp/8.14/pr-5530

Conversation

@mergify

@mergify mergify Bot commented Jul 9, 2024

Copy link
Copy Markdown
Contributor

This is a twin PR of #5496. It adds the BYO LLM guide to the ESS docs. I also took this opportunity to rename the files in the AI for security section for better organization (keeping docs in the same section next to each other, more consistent titles for landing pages) so multiple files were changed, but the only one in need of an actual proof read is the BYO LLM guide.

Preview: Connect to your own local LLM


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

* Create BYO LLM guide in ESS docs. Renames files in the AI for sec section for better organization

* minor bugfixes

* Update docs/AI-for-security/connect-to-byo.asciidoc

Co-authored-by: natasha-moore-elastic <137783811+natasha-moore-elastic@users.noreply.github.com>

* Update docs/AI-for-security/connect-to-byo.asciidoc

Co-authored-by: natasha-moore-elastic <137783811+natasha-moore-elastic@users.noreply.github.com>

* Update docs/AI-for-security/connect-to-byo.asciidoc

Co-authored-by: natasha-moore-elastic <137783811+natasha-moore-elastic@users.noreply.github.com>

* Update docs/AI-for-security/connect-to-byo.asciidoc

* Update connector-guides-landing-pg.asciidoc

---------

Co-authored-by: natasha-moore-elastic <137783811+natasha-moore-elastic@users.noreply.github.com>
(cherry picked from commit d9968da)
@mergify
mergify Bot requested a review from a team as a code owner July 9, 2024 15:46
@mergify mergify Bot added the backport label Jul 9, 2024
@github-actions

github-actions Bot commented Jul 9, 2024

Copy link
Copy Markdown

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 merged commit ce04a5e into 8.14 Jul 9, 2024
@mergify
mergify Bot deleted the mergify/bp/8.14/pr-5530 branch July 9, 2024 16:18
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