Fix inconsistencies with referencing my-rhdh-secrets

Author: GitHub Actions

modules/configuring/proc-mounting-additional-files-in-your-custom-configuration-using-rhdh-operator.adoc

@@ -47,7 +47,7 @@ data:
 apiVersion: v1
 kind: Secret
 metadata:
-  name: {my-product-secrets}
+  name: `{my-product-secrets}`
 StringData:
   secret11.txt: |
     secret-content
@@ -69,7 +69,7 @@ spec:
           key: file12.txt
           mountPath: /my/my-rhdh-config-map/path
       secrets:
-        - name: {my-product-secrets}
+        - name: `{my-product-secrets}`
           key: secret11.txt
           mountPath: /my/my-rhdh-secret/path
 

modules/configuring/proc-provisioning-your-custom-configuration.adoc

@@ -75,7 +75,7 @@ Alternatively, link:https://docs.redhat.com/en/documentation/openshift_container
 +
 [source,terminal,subs="+attributes,+quotes"]
 ----
-$ oc create secret generic {my-product-secrets} --from-file={my-product-secrets}.txt --namespace={my-product-namespace}
+$ oc create secret generic `{my-product-secrets}` --from-file=`{my-product-secrets}.txt` --namespace={my-product-namespace}
 ----
 +
 Alternatively,

modules/configuring/proc-using-the-operator-to-run-rhdh-with-your-custom-configuration.adoc

@@ -31,7 +31,7 @@ spec:
          - name: {my-app-config-config-map}
     extraEnvs:
       secrets:
-         - name: {my-product-secrets}
+         - name: `{my-product-secrets}`
     extraFiles:
       mountPath: /opt/app-root/src
     replicas: 1
@@ -60,7 +60,7 @@ spec:
     dynamicPluginsConfigMapName: dynamic-plugins-rhdh
     extraEnvs:
       secrets:
-         - name: {my-product-secrets}
+         - name: `{my-product-secrets}`
          - name: {my-product-database-secrets}
     extraFiles:
       mountPath: /opt/app-root/src
@@ -144,7 +144,7 @@ spec:
   application:
     extraEnvs:
       secrets:
-         - name: {my-product-secrets}
+         - name: `{my-product-secrets}`
 ----
 ====
 +
@@ -156,7 +156,7 @@ spec:
   application:
     extraEnvs:
       secrets:
-         - name: {my-product-secrets}
+         - name: `{my-product-secrets}`
          - name: {my-product-database-secrets}
 ----
 ====

modules/customizing/proc-customizing-the-backend-secret.adoc

@@ -16,7 +16,7 @@ Use a unique value for each {product-short} instance.
 +
 [source,terminal,subs="+attributes"]
 ----
-$ echo > {my-product-secrets}.txt "BACKEND_SECRET=$(node -p 'require("crypto").randomBytes(24).toString("base64")')"
+$ echo > `{my-product-secrets}.txt` "BACKEND_SECRET=$(node -p 'require("crypto").randomBytes(24).toString("base64")')"
 ----
 +
 .`{my-product-secrets}.txt` example

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-product-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-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.
+<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-eks.adoc

@@ -52,7 +52,7 @@ data:
 apiVersion: v1
 kind: Secret
 metadata:
-  name: {my-product-secrets}
+  name: `{my-product-secrets}`
 stringData:
   # TODO: See https://backstage.io/docs/auth/service-to-service-auth/#setup
   BACKEND_SECRET: "xxx"
@@ -103,7 +103,7 @@ spec:
         - name: "app-config-rhdh"
     extraEnvs:
       secrets:
-        - name: {my-product-secrets}
+        - name: `{my-product-secrets}`
 ----
 --
 

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

@@ -48,7 +48,7 @@ data:
 . Create a Secret named {my-product-secret} and add a key named `BACKEND_SECRET` with a `Base64-encoded` string as value:
 +
 --
-.{my-product-secrets} fragment
+.`{my-product-secrets}` fragment
 [source,yaml]
 ----
 apiVersion: v1

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

@@ -114,7 +114,7 @@ data:
 ----
 --
 
-. 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:
+. 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]