Skip to content

Commit f2d5aa2

Browse files
GitHub Actionsjmagak
authored andcommitted
RHIDP-6130 Update docs to refer to new secret name
1 parent 78e21c3 commit f2d5aa2

File tree

3 files changed

+10
-10
lines changed

3 files changed

+10
-10
lines changed

modules/configuring-external-databases/proc-configuring-postgresql-instance-using-helm.adoc

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -76,7 +76,7 @@ EOF
7676

7777
. Configure your PostgreSQL instance in the Helm configuration file named `values.yaml`:
7878
+
79-
[source,yaml, subs="+attributes"]
79+
[source,yaml,subs="+quotes,+attributes"]
8080
----
8181
# ...
8282
upstream:
@@ -136,11 +136,11 @@ upstream:
136136
name: dynamic-plugins
137137
optional: true
138138
name: dynamic-plugins
139-
- name: dynamic-plugins-npmrc
139+
- name: `_<release_name>_-dynamic-plugins-npmrc`
140140
secret:
141141
defaultMode: 420
142142
optional: true
143-
secretName: dynamic-plugins-npmrc
143+
secretName: `_<release_name>_-dynamic-plugins-npmrc`
144144
- name: postgres-crt
145145
secret:
146146
secretName: {my-product-database-certificates-secrets} <7>

modules/dynamic-plugins/proc-install-plugins-using-custom-npm-registry.adoc

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -5,16 +5,16 @@
55

66
You can install external plugins in an air-gapped environment by setting up a custom NPM registry.
77

8-
You can configure the NPM registry URL and authentication information for dynamic plugin packages using a Helm chart. For dynamic plugin packages obtained through `npm pack`, you can use a `.npmrc` file.
8+
You can configure the NPM registry URL and authentication information for dynamic plugin packages using a Helm chart. For dynamic plugin packages obtained through `npm pack`, you can use a `.npmrc` file.
99

10-
Using the Helm chart, add the `.npmrc` file to the NPM registry by creating a secret named `dynamic-plugins-npmrc` with the following content:
10+
Using the Helm chart, add the `.npmrc` file to the NPM registry by creating a secret. For example:
1111

12-
[source,yaml]
12+
[source,yaml,subs="+quotes,+attributes"]
1313
----
1414
apiVersion: v1
1515
kind: Secret
1616
metadata:
17-
name: dynamic-plugins-npmrc
17+
name: `_<release_name>_-dynamic-plugins-npmrc`
1818
type: Opaque
1919
stringData:
2020
.npmrc: |

modules/dynamic-plugins/proc-load-plugin-js-package.adoc

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -46,12 +46,12 @@ registry=<registry-url>
4646
* Create a secret with the `.npmrc` content as follows:
4747
+
4848
.Example secret configuration
49-
[source,yaml]
49+
[source,yaml,subs="+quotes,+attributes"]
5050
----
5151
apiVersion: v1
5252
kind: Secret
5353
metadata:
54-
name: dynamic-plugins-npmrc
54+
name: `_<release_name>_-dynamic-plugins-npmrc`
5555
type: Opaque
5656
stringData:
5757
.npmrc: |
@@ -61,7 +61,7 @@ stringData:
6161

6262
* For {product-very-short} Helm chart, name the secret using the following format for automatic mounting:
6363
+
64-
`<release-name>-dynamic-plugins-npmrc`
64+
`_<release_name>_-dynamic-plugins-npmrc`
6565
--
6666

6767
. To apply the changes, restart the {product-very-short} application.

0 commit comments

Comments
 (0)