RHIDP-3206: Added missing attribute declaration in the source code (#945)

* Added missing attribute declaration in the source code

* Updated env variables

Author: pabel-rh

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

@@ -19,12 +19,11 @@ You can configure an external PostgreSQL instance by using the Helm Chart. By de
 By default, {product-short} uses a database for each plugin and automatically creates it if none is found. You might need the `Create Database` privilege in addition to `PSQL Database` privileges for configuring an external PostgreSQL instance.
 ====
 
-
 .Procedure
 
 . Optional: Create a certificate secret to configure your PostgreSQL instance with a TLS connection:
 +
-[source,terminal]
+[source,terminal,subs="+attributes"]
 ----
 cat <<EOF | oc -n <your-namespace> create -f -
 apiVersion: v1
@@ -52,7 +51,7 @@ EOF
 
 . Create a credential secret to connect with the PostgreSQL instance:
 +
-[source,terminal]
+[source,terminal,subs="+attributes"]
 ----
 cat <<EOF | oc -n <your-namespace> create -f -
 apiVersion: v1
@@ -76,7 +75,7 @@ EOF
 
 . Configure your PostgreSQL instance in the Helm configuration file named `values.yaml`:
 +
-[source,yaml]
+[source,yaml,subs="+attributes"]
 ----
 # ...
 upstream:
@@ -89,10 +88,10 @@ upstream:
       backend:
         database:
           connection:  # configure Backstage DB connection parameters
-            host: ${POSTGRES_HOST}
-            port: ${POSTGRES_PORT}
-            user: ${POSTGRES_USER}
-            password: ${POSTGRES_PASSWORD}
+            host: $\{POSTGRES_HOST}
+            port: $\{POSTGRES_PORT}
+            user: $\{POSTGRES_USER}
+            password: $\{POSTGRES_PASSWORD}
             ssl:
               rejectUnauthorized: true,
               ca:

modules/configuring-external-databases/proc-migrating-databases-to-an-external-server.adoc

@@ -81,7 +81,7 @@ You can stop port forwarding when the copying of the data is complete. For more
 . Reconfigure your `{product-custom-resource-type}` custom resource (CR). For more information, see link:{configuring-book-url}#proc-configuring-postgresql-instance-using-operator_configuring-external-postgresql-databases[Configuring an external PostgreSQL instance using the Operator].
 . Check that the following code is present at the end of your `Backstage` CR after reconfiguration:
 +
-[source,yaml]
+[source,yaml,subs="+attributes"]
 ----
 # ...
 spec:

modules/dynamic-plugins/proc-create-plugin-tgz-file.adoc

@@ -48,7 +48,7 @@ npm pack --pack-destination ~/test/dynamic-plugins-root/
 To create a plugin registry using HTTP server on {ocp-short}, run the following commands:
 
 .Example commands to build and deploy an HTTP server in {ocp-short}
-[source,terminal]
+[source,terminal, subs="+attributes"]
 ----
 oc project {my-product-namespace}
 oc new-build httpd --name=plugin-registry --binary

modules/installation/proc-install-rhdh-airgapped-environment-ocp-helm.adoc

@@ -92,7 +92,7 @@ If an x509 error occurs, verify that you have link:https://access.redhat.com/sol
 
 . Use the following command to verify that both images are present in the internal {ocp-short} registry:
 +
-[source,terminal]
+[source,terminal, subs="+attributes"]
 ----
 oc get imagestream -n {my-product-namespace}
 ----