You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: modules/developer-lightspeed/proc-changing-your-llm-provider.adoc
+29-9Lines changed: 29 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,20 +16,40 @@ The LLM provider configuration section includes a mandatory dummy provider block
16
16
17
17
.Procedure
18
18
19
-
You can define additional LLM providers using one of two methods.
19
+
You can define additional LLM providers using either of following methods:
20
20
21
-
* Recommended: In your Developer Lightspeed plugin configuration (For example, the `lightspeed` section within the `lightspeed-app-config.yaml` file), define the new provider or providers under the `lightspeed.servers` key as shown in the following code:
21
+
* Recommended: In your Developer Lightspeed plugin configuration (the `lightspeed` section within the `lightspeed-app-config.yaml` file), define the new provider or providers under the `lightspeed.servers` key as shown in the following code:
22
22
+
23
23
[source,yaml]
24
24
----
25
25
lightspeed:
26
26
servers:
27
-
- id: my-new-provider
28
-
url: my-new-url
29
-
token: my-new-token
27
+
- id: _<my_new_provider>_
28
+
url: _<my_new_url>_
29
+
token: _<my_new_token>_
30
30
----
31
-
32
-
* Alternatively, you can add new LLM providers by updating the rcsconfig.yaml file.
31
+
** Alternatively, you can set the `id`, `url`, and `token` values in a Kubernetes Secret and reference them using environment variables in your application configuration as shown in the following code:
32
+
+
33
+
[source,yaml]
34
+
----
35
+
env:
36
+
- name: _<my_new_url>_
37
+
valueFrom:
38
+
secretKeyRef:
39
+
name: my-secret
40
+
key: _<my_new_url>_
41
+
- name: _<my_new_provider>_
42
+
valueFrom:
43
+
secretKeyRef:
44
+
name: my-secret
45
+
key: _<my_new_provider>_
46
+
- name: _<my_new_token>_
47
+
valueFrom:
48
+
secretKeyRef:
49
+
name: my-secret
50
+
key: _<my_new_token>_
51
+
----
52
+
* You can add new LLM providers by updating the `rcsconfig.yaml` file.
33
53
.. In the `llm_providers` section within your `rcsconfig.yaml` file, add your new provider configuration below the mandatory dummy provider block as shown in the following code:
0 commit comments