Fix inconsistencies with referencing my-rhdh-secrets (redhat-developer#918)

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

Author: jmagak

modules/dynamic-plugins/proc-config-dynamic-plugins-rhdh-operator.adoc

@@ -10,7 +10,7 @@ You can store the configuration for dynamic plugins in a `ConfigMap` object that
 
 [NOTE]
 ====
-If the `pluginConfig` field references environment variables, you must define the variables in your `my-rhdh-secrets` secret.
+If the `pluginConfig` field references environment variables, you must define the variables in your {my-product-secrets} secret.
 ====
 
 .Procedure

modules/installation/proc-configuring-an-rhdh-instance-with-tls-in-kubernetes.adoc

@@ -119,8 +119,8 @@ data:
 <1> The base URL to the Kubernetes control plane. You can run the `kubectl cluster-info` command to get the base URL.
 <2> Set the value of this parameter to `false` to enable the verification of the TLS certificate.
 <3> Optional: The link to the Kubernetes dashboard managing the ARO cluster.
-<4> Optional: Pass the service account token using a `K8S_SERVICE_ACCOUNT_TOKEN` environment variable that you can define in your `my-rhdh-secrets` secret.
-<5> Pass the CA data using a `K8S_CONFIG_CA_DATA` environment variable that you can define in your `my-rhdh-secrets` secret.
+<4> Optional: Pass the service account token using a `K8S_SERVICE_ACCOUNT_TOKEN` environment variable that you can define in your {my-product-secrets} secret.
+<5> Pass the CA data using a `K8S_CONFIG_CA_DATA` environment variable that you can define in your {my-product-secrets} secret.
 
 . Save the configuration changes.
 

modules/installation/proc-deploy-rhdh-instance-gke.adoc

@@ -45,16 +45,16 @@ data:
 ----
 --
 
-. Create a Secret named `my-rhdh-secrets` and add a key named `BACKEND_SECRET` with a `Base64-encoded` string as value:
+. Create a Secret named {my-product-secret} and add a key named `BACKEND_SECRET` with a `Base64-encoded` string as value:
 +
 --
-.`my-rhdh-secrets` fragment
+.{my-product-secrets} fragment
 [source,yaml]
 ----
 apiVersion: v1
 kind: Secret
 metadata:
-  name: my-rhdh-secrets
+  name: {my-product-secret}
 stringData:
   # TODO: See https://backstage.io/docs/auth/service-to-service-auth/#setup
   BACKEND_SECRET: "xxx"
@@ -106,7 +106,7 @@ spec:
         - name: "app-config-rhdh"
     extraEnvs:
       secrets:
-        - name: "my-rhdh-secrets"
+        - name: {my-product-secret}
 ----
 --
 

modules/installation/proc-rhdh-deploy-aks-operator.adoc

@@ -114,15 +114,15 @@ data:
 ----
 --
 
-. Create a Secret named `my-rhdh-secrets` and add a key named `BACKEND_SECRET` with a `Base64-encoded` string value as shown in the following example:
+. Create a Secret named {my-product-secrets} and add a key named `BACKEND_SECRET` with a `Base64-encoded` string value as shown in the following example:
 +
 --
 [source,yaml]
 ----
 apiVersion: v1
 kind: Secret
 metadata:
-  name: my-rhdh-secrets
+  name: {my-product-secret}
 stringData:
   BACKEND_SECRET: "xxx"
 ----
@@ -146,7 +146,7 @@ spec:
         - name: "app-config-rhdh"
     extraEnvs:
       secrets:
-        - name: "my-rhdh-secrets"
+        - name: {my-product-secret}
 ----
 --