RHIDP-6130: Update docs to refer to new secret name (redhat-developer#962)

* Update docs to refer to new secret name

RHIDP-6130 Update docs to refer to new secret name

RHIDP-6130 Update docs to refer to new secret name

* RHIDP-6130 Update docs to refer to new secret name

* RHIDP-6130 Update docs to refer to new secret name

---------

Co-authored-by: GitHub Actions <[email protected]>

Author: jmagak

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

@@ -76,7 +76,7 @@ EOF
 
 . Configure your PostgreSQL instance in the Helm configuration file named `values.yaml`:
 +
-[source,yaml, subs="+attributes"]
+[source,yaml,subs="+quotes,+attributes"]
 ----
 # ...
 upstream:
@@ -140,7 +140,7 @@ upstream:
       secret:
         defaultMode: 420
         optional: true
-        secretName: dynamic-plugins-npmrc
+        secretName: '{{ printf "%s-dynamic-plugins-npmrc" .Release.Name }}'
     - name: postgres-crt
       secret:
         secretName: {my-product-database-certificates-secrets} <7>

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

@@ -5,20 +5,21 @@
 
 You can install external plugins in an air-gapped environment by setting up a custom NPM registry.
 
-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. 
+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.
 
-Using the Helm chart, add the `.npmrc` file to the NPM registry by creating a secret named `dynamic-plugins-npmrc` with the following content:
+Using the Helm chart, add the `.npmrc` file to the NPM registry by creating a secret. For example:
 
-[source,yaml]
+[source,yaml,subs="+quotes,+attributes"]
 ----
 apiVersion: v1
 kind: Secret
 metadata:
-  name: dynamic-plugins-npmrc
+  name: `_<release_name>_-dynamic-plugins-npmrc` # <1>
 type: Opaque
 stringData:
   .npmrc: |
     registry=<registry-url>
     //<registry-url>:_authToken=<auth-token>
           ...
 ----
+<1> Replace `_<release_name>_` with your Helm release name. This name is a unique identifier for each chart installation in the Kubernetes cluster.

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

@@ -43,25 +43,26 @@ registry=<registry-url>
 . When using {ocp-short} or Kubernetes:
 +
 --
-* Create a secret with the `.npmrc` content as follows:
+* Use the Helm chart to add the `.npmrc` file by creating a secret. For example:
 +
 .Example secret configuration
-[source,yaml]
+[source,yaml,subs="+quotes,+attributes"]
 ----
 apiVersion: v1
 kind: Secret
 metadata:
-  name: dynamic-plugins-npmrc
+  name: `_<release_name>_-dynamic-plugins-npmrc` # <1>
 type: Opaque
 stringData:
   .npmrc: |
     registry=<registry-url>
     //<registry-url>:_authToken=<auth-token>
 ----
+<1> Replace `_<release_name>_` with your Helm release name. This name is a unique identifier for each chart installation in the Kubernetes cluster.
 
 * For {product-very-short} Helm chart, name the secret using the following format for automatic mounting:
 +
-`<release-name>-dynamic-plugins-npmrc`
+`_<release_name>_-dynamic-plugins-npmrc`
 --
 
 . To apply the changes, restart the {product-very-short} application.