Merge branch 'release-1.4' into plugins-table-update-1.4.2

Author: nickboldt

artifacts/rhdh-plugins-reference/keycloak/keycloak-plugin-admin.adoc

@@ -1,5 +1,5 @@
 [id="rhdh-keycloak_{context}"]
-= Installing and configuring Keycloak 
+= Installing and configuring Keycloak
 
 The Keycloak backend plugin, which integrates Keycloak into {product-short}, has the following capabilities:
 
@@ -8,7 +8,7 @@ The Keycloak backend plugin, which integrates Keycloak into {product-short}, has
 
 [NOTE]
 ====
-The supported Keycloak version is `{keycloak-version}`.
+The supported {rhbk-brand-name} ({rhbk}) version is `{keycloak-version}`.
 ====
 
 == Installation

assemblies/assembly-release-notes-fixed-security-issues.adoc

@@ -8,11 +8,12 @@ This section lists security issues fixed in {product} {product-version}.
 
 include::./modules/release-notes/snip-fixed-security-issues-in-product-1.4.1.adoc[leveloffset=+2]
 
-// nothing yet so don't include this 
+// nothing yet so don't include this
 // include::./modules/release-notes/snip-fixed-security-issues-in-rpm-1.4.1.adoc[leveloffset=+2]
 
 == {product} 1.4.0
 
-include::./modules/release-notes/snip-fixed-security-issues-in-product-1.3.0.adoc[leveloffset=+2]
+include::./modules/release-notes/snip-fixed-security-issues-in-product-1.4.0.adoc[leveloffset=+2]
 
-include::./modules/release-notes/snip-fixed-security-issues-in-rpm-1.3.0.adoc[leveloffset=+2]
+// nothing yet so don't include this
+//include::./modules/release-notes/snip-fixed-security-issues-in-rpm-1.4.0.adoc[leveloffset=+2]

modules/about/ref-supported-platforms.adoc

@@ -8,7 +8,3 @@
 
 You can find the supported platforms and life cycle dates for both current and past versions of {product} on the link:https://access.redhat.com/support/policy/updates/developerhub[Life Cycle page].
 
-[role="_additional-resources"]
-.Additional resources
-
-* link:https://redhat-developer.github.io/red-hat-developers-documentation-rhdh/pr-837/rel-notes-rhdh/#compatibility-matrix[{product} {product-version} Compatibility Matrix].

modules/authentication/proc-enabling-authentication-with-github.adoc

@@ -55,7 +55,7 @@ TIP: If you plan to make changes using the GitHub API, ensure that `Read and wri
 +
 `AUTH_GITHUB_APP_ID`:: Enter the saved **App ID**.
 `AUTH_GITHUB_CLIENT_ID`:: Enter the saved **Client ID**.
-`GITHUB_HOST_DOMAIN`:: Enter your GitHub host domain: `github.com` unless you are using GitHub Enterprise.
+//`GITHUB_HOST_DOMAIN`:: Enter your GitHub host domain: `github.com` unless you are using GitHub Enterprise.
 `GITHUB_ORGANIZATION`:: Enter your GitHub organization name, such as `__<your_github_organization_name>__'.
 `GITHUB_ORG_URL`:: Enter `$GITHUB_HOST_DOMAIN/$GITHUB_ORGANIZATION`.
 `GITHUB_CLIENT_SECRET`:: Enter the saved **Client Secret**.
@@ -145,6 +145,7 @@ auth:
         callbackUrl: __<your_intermediate_service_url/handler>__
 ----
 
+////
 `enterpriseInstanceUrl`::
 Your GitHub Enterprise URL.
 Requires you defined the `GITHUB_HOST_DOMAIN` secret in the previous step.
@@ -158,6 +159,7 @@ auth:
       production:
         enterpriseInstanceUrl: ${GITHUB_HOST_DOMAIN}
 ----
+////
 
 [TIP]
 ====

modules/authorization/proc-defining-authorizations-in-external-files-by-using-the-operator.adoc

@@ -75,9 +75,9 @@ $ oc create configmap rbac-policies \
      --from-file=rbac-conditional-policies.yaml
 ----
 
-. Update your {product-short} `Backstage` custom resource to mount in the {product-short} filesystem your files from the `rbac-policies` config map:
+. Update link:{configuring-book-url}[your `{product-custom-resource-type}` custom resource] to mount in the {product-short} filesystem your files from the `rbac-policies` config map:
 +
-.`Backstage` Custom resource fragment
+.`{product-custom-resource-type}` custom resource fragment
 [source,yaml]
 ----
 apiVersion: rhdh.redhat.com/v1alpha3

modules/configuring-a-proxy/proc-configuring-proxy-in-operator-deployment.adoc

@@ -59,7 +59,7 @@ For Operator-based deployment, the approach you use for proxy configuration is b
 ----
 
 
-* As a developer, set the proxy information in your custom resource (CR) file as shown in the following example:
+* As a developer, set the proxy information in your `{product-custom-resource-type}` CR file as shown in the following example:
 + 
 .Example: Setting proxy variables in a CR file
 [source, yaml]

modules/configuring-deployment/proc-configuring-deployment-by-using-the-operator.adoc

@@ -1,17 +1,17 @@
 [id="configuring-the-deployment"]
-= Configuring {product} deployment when using the operator
+= Configuring {product} deployment when using the Operator
 
-The {product} operator exposes a `rhdh.redhat.com/v1alpha2` API Version of its Custom Resource Definition (CRD). This CRD exposes a generic `spec.deployment.patch` field, which gives you full control over the {product-short} Deployment resource. This field can be a fragment of the standard `apps.Deployment` Kubernetes object.
+The {product} Operator exposes a `rhdh.redhat.com/v1alpha3` API Version of its custom resource (CR). This CR exposes a generic `spec.deployment.patch` field, which gives you full control over the {product-short} Deployment resource. This field can be a fragment of the standard `apps.Deployment` Kubernetes object.
 
 .Procedure
 
-. Create a {product-short} Custom Resource Definition with the following fields:
+. Create a `{product-custom-resource-type}` CR with the following fields:
 
 --
 .Example
 [source, yaml]
 ----
-apiVersion: rhdh.redhat.com/v1alpha2
+apiVersion: rhdh.redhat.com/v1alpha3
 kind: Backstage
 metadata:
   name: developer-hub
@@ -28,7 +28,7 @@ Add labels to the {product-short} pod.
 .Example adding the label `my=true`
 [source, yaml]
 ----
-apiVersion: rhdh.redhat.com/v1alpha2
+apiVersion: rhdh.redhat.com/v1alpha3
 kind: Backstage
 metadata:
   name: developer-hub
@@ -50,7 +50,7 @@ Add an additional volume named `my-volume` and mount it under `/my/path` in the
 .Example additional volume
 [source, yaml]
 ----
-apiVersion: rhdh.redhat.com/v1alpha2
+apiVersion: rhdh.redhat.com/v1alpha3
 kind: Backstage
 metadata:
   name: developer-hub
@@ -78,7 +78,7 @@ Replace the default `dynamic-plugins-root` volume with a persistent volume claim
 .Example `dynamic-plugins-root` volume replacement
 [source, yaml]
 ----
-apiVersion: rhdh.redhat.com/v1alpha2
+apiVersion: rhdh.redhat.com/v1alpha3
 kind: Backstage
 metadata:
   name: developer-hub
@@ -103,7 +103,7 @@ Set the CPU request for the {product-short} application container to 250m.
 .Example CPU request
 [source, yaml]
 ----
-apiVersion: rhdh.redhat.com/v1alpha2
+apiVersion: rhdh.redhat.com/v1alpha3
 kind: Backstage
 metadata:
   name: developer-hub
@@ -127,7 +127,7 @@ Add a new `my-sidecar` sidecar container into the {product-short} Pod.
 .Example side car container
 [source, yaml]
 ----
-apiVersion: rhdh.redhat.com/v1alpha2
+apiVersion: rhdh.redhat.com/v1alpha3
 kind: Backstage
 metadata:
   name: developer-hub

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

@@ -74,7 +74,7 @@ EOF
 <3> Optional: Provide the value based on the required link:https://www.postgresql.org/docs/15/libpq-connect.html#LIBPQ-CONNECT-SSLMODE[Secure Sockets Layer (SSL) mode].
 <4> Optional: Provide the value only if you need a TLS connection for your PostgreSQL instance.
 
-. Create a `{product-custom-resource-type}` custom resource (CR):
+. Create your `{product-custom-resource-type}` custom resource (CR):
 +
 [source,terminal,subs="+attributes,+quotes"]
 ----

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

@@ -78,7 +78,7 @@ done
 You can stop port forwarding when the copying of the data is complete. For more information about handling large databases and using the compression tools, see the link:https://www.postgresql.org/docs/current/backup-dump.html#BACKUP-DUMP-LARGE[Handling Large Databases] section on the PostgreSQL website.
 ====
 
-. Reconfigure your `Backstage` 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].
+. 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]

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

@@ -21,7 +21,28 @@ It contains one secret per line in `KEY=value` form.
 . Author your custom `{my-app-config-file}` file.
 This is the main {product-short} configuration file.
 +
-You can start with an empty file to use the default configuration.
+The `baseUrl` field is mandatory in your `{my-app-config-file}` file to ensure proper functionality of {product-short}. You must specify the `baseUrl` in both the `app` and `backend` sections to avoid errors during initialization.
++
+.Configuring the `baseUrl` in `{my-app-config-file}`
+====
+[source,yaml,subs="+attributes,+quotes"]
+----
+app:
+  title: {product}
+  baseUrl: {my-product-url}
+
+backend:
+  auth:
+    externalAccess:
+      - type: legacy
+        options:
+          subject: legacy-default-config
+          secret: "${BACKEND_SECRET}"
+  baseUrl: {my-product-url}
+  cors:
+    origin: {my-product-url}
+----
+====
 +
 Optionally, enter your configuration such as: