Merge pull request #2659 from EnterpriseDB/release/2022-05-12a

Release/2022 05 12a

advocacy_docs/supported-open-source/cloud_native_pg/index.mdx

@@ -28,7 +28,6 @@ redirects:
   - /postgres_for_kubernetes/latest/connection_pooling/
   - /postgres_for_kubernetes/latest/kubernetes_upgrade/
   - /postgres_for_kubernetes/latest/expose_pg_services/
-  - /postgres_for_kubernetes/latest/cnp-plugin/
   - /postgres_for_kubernetes/latest/failover/
   - /postgres_for_kubernetes/latest/troubleshooting/
   - /postgres_for_kubernetes/latest/fencing/
@@ -43,8 +42,17 @@ redirects:
 CloudNativePG is the Kubernetes operator that covers the full lifecycle of a highly available Postgres database cluster with a primary/standby architecture, using native streaming replication.
 
 !!! Note
-    Looking for CloudNativePG documentation? Head over to [cloudnative-pg.io/docs/](https://cloudnative-pg.io/docs/).
+    Looking for CloudNativePG documentation? Head over to [cloudnative-pg.io/docs/](https://cloudnative-pg.io/documentation/1.15.0/).
 
 CloudNativePG was originally built by EDB, then released open source under Apache License 2.0 and submitted for CNCF Sandbox in April 2022. The source code repository is in [Github](https://github.com/cloudnative-pg/cloudnative-pg).
 
+Key features available include:
+- Kubernetes API integration for high availability
+- Self-healing through failover and automated recreation of replicas
+- Capacity management with scale up/down capabilities
+- Planned switchovers for scheduled maintenance
+- Read-only and read-write Kubernetes services definitions
+- Rolling updates for Postgres minor versions and operator upgrades
+- Continuous backup and point-in-time recovery
+
 

gatsby-node.js

@@ -154,6 +154,7 @@ exports.createPages = async ({ actions, graphql, reporter }) => {
         nodes {
           id
           relativePath
+          sourceInstanceName
         }
       }
     }
@@ -163,17 +164,16 @@ exports.createPages = async ({ actions, graphql, reporter }) => {
     reporter.panic("createPages graphql query has errors!", result.errors);
   }
 
-  processFileNodes(result.data.allFile.nodes, actions);
-
   // this is critical to avoiding excessive Netlify deploy times: it ensures the pages are ordered consistently from build to build
   result.data.allMdx.nodes = result.data.allMdx.nodes.sort((a, b) =>
     a.fields.path.localeCompare(b.fields.path),
   );
 
   const { nodes } = result.data.allMdx;
-
   const productVersions = buildProductVersions(nodes);
 
+  processFileNodes(result.data.allFile.nodes, productVersions, actions);
+
   // it should be possible to remove these in the future,
   // they are only used for navLinks generation
   const learn = nodes.filter((file) => file.fields.docType === "advocacy");
@@ -426,10 +426,29 @@ const createAdvocacy = (navTree, prevNext, doc, learn, actions) => {
   });
 };
 
-const processFileNodes = (fileNodes, actions) => {
+const processFileNodes = (fileNodes, productVersions, actions) => {
   fileNodes.forEach((node) => {
+    const product =
+      node.sourceInstanceName === "advocacy_docs"
+        ? ""
+        : node.sourceInstanceName;
+    const version = node.relativePath.split(path.sep)[0];
+    const isLatest = product ? productVersions[product][0] === version : false;
+    let urlPath = path.join(path.sep, product, node.relativePath);
+    if (isLatest) {
+      const latestPath = replacePathVersion(urlPath);
+      actions.createRedirect({
+        fromPath: urlPath,
+        toPath: latestPath,
+        redirectInBrowser: true,
+        isPermanent: false,
+        force: true,
+      });
+      urlPath = latestPath;
+    }
+
     actions.createPage({
-      path: node.relativePath,
+      path: urlPath,
       component: require.resolve("./src/templates/file.js"),
       context: {
         nodeId: node.id,

product_docs/docs/efm/4/05_using_efm.mdx

@@ -221,6 +221,8 @@ The following parameters must be unique in each cluster properties file:
  `db.data.dir`
 
  `virtual.ip` (if used)
+
+ `db.service.name` (if used)
 
 In each cluster properties file, the `db.port` parameter specifies a unique value for each cluster. The `db.user` and `db.database` parameter can have the same value or a unique value. For example, the `acctg.properties` file can specify:
 

product_docs/docs/postgres_for_kubernetes/1/cloudnativepg.mdx

@@ -20,6 +20,6 @@ As a general rule, all features available in the open source CloudNativePG are
 also available in EDB Postgres for Kubernetes - provided the correct API
 version is used.
 
-For this reason, we refer to the CloudNativePG for detailed information on the
+Refer to the [CloudNativePG documentation](https://cloudnative-pg.io/documentation/1.15.0/) for detailed information on the
 available features.