RHDHBUGS-2051: Adding a new topic on adding a new llm provider

[pabel-rh]

IMPORTANT: Do Not Merge - To be merged by Docs Team Only

Version(s):
main, 1.7.x
Issue:
RHDHBUGS-2051
Preview:

• https://redhat-developer.github.io/red-hat-developers-documentation-rhdh/pr-1403/developer-lightspeed/#customizing-developer-lightspeed
• https://redhat-developer.github.io/red-hat-developers-documentation-rhdh/pr-1403/developer-lightspeed/#proc-installing-and-configuring-lightspeed_developer-lightspeed

[rhdh-bot]

Updated preview: https://redhat-developer.github.io/red-hat-developers-documentation-rhdh/pr-1403/ @ 09/23/25 09:59:03

[Jdubrick]

looks better to me. @benwilcock wdyt?

[jmagak]

Just a few suggestions, @pabel-rh.

[benwilcock]

Looks better, thanks folks. /lgtm

[jmagak]

/cherry-pick release-1.7

[openshift-cherrypick-robot]

@jmagak: once the present PR merges, I will cherry-pick it on top of release-1.7 in a new PR and assign it to you.

In response to this:

/cherry-pick release-1.7

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[openshift-cherrypick-robot]

@jmagak: #1403 failed to apply on top of branch "release-1.7":

Applying: First draft
Applying: Included content for adding a new llm provider
Using index info to reconstruct a base tree...
M	artifacts/attributes.adoc
M	assemblies/assembly-customizing-developer-lightspeed.adoc
M	modules/developer-lightspeed/proc-installing-and-configuring-lightspeed.adoc
Falling back to patching base and 3-way merge...
Auto-merging modules/developer-lightspeed/proc-installing-and-configuring-lightspeed.adoc
Auto-merging assemblies/assembly-customizing-developer-lightspeed.adoc
CONFLICT (content): Merge conflict in assemblies/assembly-customizing-developer-lightspeed.adoc
Auto-merging artifacts/attributes.adoc
CONFLICT (content): Merge conflict in artifacts/attributes.adoc
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config advice.mergeConflict false"
Patch failed at 0002 Included content for adding a new llm provider

In response to this:

/cherry-pick release-1.7

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.