Merge pull request #1524 from EnterpriseDB/release/2021-07-01

Release: 2021-07-01
Former-commit-id: 4697aeb

Author: josh-heyer

.devcontainer/devcontainer.json

@@ -21,7 +21,7 @@
 	"appPort": [8000],
 
 	// Use 'postCreateCommand' to run commands after the container is created.
-	"postCreateCommand": "yarn install && git submodule update --init",
+	"postCreateCommand": "yarn install",
 
 	// docker in docker (https://github.com/microsoft/vscode-dev-containers/blob/master/script-library/docs/docker-in-docker.md)
 	"runArgs": ["--init", "--privileged"],

.github/workflows/deploy-develop.yml

@@ -15,8 +15,6 @@ jobs:
       with:
         ref: develop
         fetch-depth: 0 # fetch whole repo so git-restore-mtime can work
-    - name: Update submodules
-      run: git submodule update --init --remote
     - name: Adjust file watchers limit
       run: echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf && sudo sysctl -p
 

.github/workflows/deploy-main.yml

@@ -15,8 +15,6 @@ jobs:
       with:
         ref: main
         fetch-depth: 0 # fetch whole repo so git-restore-mtime can work
-    - name: Update submodules
-      run: git submodule update --init --remote
     - name: Adjust file watchers limit
       run: echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf && sudo sysctl -p
 

.github/workflows/update-pdfs-on-develop.yml

@@ -19,8 +19,6 @@ jobs:
       with:
         ref: develop
         ssh-key:  ${{ secrets.ADMIN_SECRET_SSH_KEY }}
-    - name: Update submodules
-      run: git submodule update --init --remote
 
     - uses: actions/setup-node@v1
       with:

.gitmodules

@@ -34,8 +34,6 @@ We recommend using MacOS to work with the EDB Docs application.
 
 1. Install all required packages by running `yarn`.
 
-1. Pull the shared icon files down with `git submodule update --init`. This needs to be run inside of the project folder, if you have cloned the repo using GitHub Desktop, ensure that you have `cd` into the project.
-
 1. And finally, you can start up the site locally with `yarn develop`, which should make it live at `http://localhost:8000/`. Huzzah!
 
 ### Installation of PDF / Doc Conversion Tools (optional)

README.md

@@ -60,19 +60,15 @@ Example:
     ```shell
     yarn
     ```
-12. Pull down shared icon files  
-    ```shell
-    git submodule update --init
-    ```
-13. Select sources with yarn  
+12. Select sources with yarn  
     ```shell
     yarn config-sources
     ```
     You'll be prompted to choose the packages you'd like to access; you can use comma separated values to choose more than one  
     ```shell
     yarn develop
     ```
-14. Go to the localhost port in your browser, e.g. http://localhost:8000/ (your url will be mentioned in Terminal)
+13. Go to the localhost port in your browser, e.g. http://localhost:8000/ (your url will be mentioned in Terminal)
 
 ### Tips to Use Terminal
 - <kbd>⌘</kbd>+<kbd>T</kbd> (press the command key and T key together) opens a new tab - use this to execute terminal commands while <code>yarn develop</code> is running
@@ -81,10 +77,10 @@ Example:
 ## How to Make changes and Submit Pull Requests
 You'll make edits and additions via your IDE (VS Code). We recommend using [Github Desktop](https://desktop.github.com/) unless you're familiar with git.  
 
-15. Get in the habit of pulling the latest changes from the `develop` branch of the Github repository on a regular basis, so that you don't have to manually merge your changes with those made by others. Use the "Fetch origin" and "Pull origin" buttons in Github Desktop at the start of your work day to update your local files with those from the server. You should also do this again before submitting a pull request. For details, see: [Syncing your branch
+14. Get in the habit of pulling the latest changes from the `develop` branch of the Github repository on a regular basis, so that you don't have to manually merge your changes with those made by others. Use the "Fetch origin" and "Pull origin" buttons in Github Desktop at the start of your work day to update your local files with those from the server. You should also do this again before submitting a pull request. For details, see: [Syncing your branch
 ](https://docs.github.com/en/desktop/contributing-and-collaborating-using-github-desktop/syncing-your-branch)
 
-16. To submit a pull request
+15. To submit a pull request
     - Make changes to the repository in VS code (or your IDE of choice)
     - Save changes (<kbd>CTRL</kbd>+<kbd>S</kbd> in VS Code)
     - Create a new branch and name it in Github Desktop

advocacy_docs/community/contributing/repo.mdx

@@ -16,7 +16,7 @@
     "build": "gatsby build --prefix-paths",
     "serve-build": "gatsby serve --prefix-paths",
     "prepare": "husky install",
-    "update-icons": "git submodule update --init --remote && node scripts/createIconTypes.js && node scripts/createIconNames.js",
+    "update-icons": "node scripts/createIconTypes.js && node scripts/createIconNames.js",
     "build-pdf": "docker-compose -f docker/docker-compose.build-pdf.yaml run --rm --entrypoint scripts/pdf/generate_pdf.py pdf-builder",
     "build-all-pdfs": "for i in product_docs/docs/**/*/ ; do echo \"$i\"; yarn build-pdf ${i%} || exit 1; done",
     "build-all-pdfs-ci": "for i in product_docs/docs/**/*/ ; do echo \"$i\"; python3 scripts/pdf/generate_pdf.py ${i%} || exit 1; done",

package.json

@@ -36,17 +36,17 @@ There are three PostgreSQL backend nodes, one Primary and two Standby nodes. Con
 backend_hostname0 = ‘server1_IP'
 backend_port0 = 5444
 backend_weight0 = 1
-backend_flag0 = 'DISALLOW_TO_FAILOVER'
+backend_flag0 = 'ALLOW_TO_FAILOVER'
 
 backend_hostname1 = ‘server2_IP'
 backend_port1 = 5444
 backend_weight1 = 1
-backend_flag1 = 'DISALLOW_TO_FAILOVER'
+backend_flag1 = 'ALLOW_TO_FAILOVER'
 
 backend_hostname2 = ‘server3_IP'
 backend_port2 = 5444
 backend_weight2 = 1
-backend_flag2 = 'DISALLOW_TO_FAILOVER'
+backend_flag2 = 'ALLOW_TO_FAILOVER'
 ```
 
 **Enable Load-balancing and streaming replication mode**
@@ -65,7 +65,7 @@ Health-checking and failover must be handled by EFM and hence, these must be dis
 
 ```text
 health_check_period = 0
-fail_over_on_backend_error = off
+failover_on_backend_error = off
 failover_if_affected_tuples_mismatch = off
 failover_command = ‘’
 failback_command = ‘’

product_docs/docs/efm/4.1/efm_pgpool_ha_guide/03_components_ha_pgpool.mdx

@@ -32,17 +32,17 @@ There are three PostgreSQL backend nodes, one Primary and two Standby nodes. Con
 backend_hostname0 = ‘server1_IP'
 backend_port0 = 5444
 backend_weight0 = 1
-backend_flag0 = 'DISALLOW_TO_FAILOVER'
+backend_flag0 = 'ALLOW_TO_FAILOVER'
 
 backend_hostname1 = ‘server2_IP'
 backend_port1 = 5444
 backend_weight1 = 1
-backend_flag1 = 'DISALLOW_TO_FAILOVER'
+backend_flag1 = 'ALLOW_TO_FAILOVER'
 
 backend_hostname2 = ‘server3_IP'
 backend_port2 = 5444
 backend_weight2 = 1
-backend_flag2 = 'DISALLOW_TO_FAILOVER'
+backend_flag2 = 'ALLOW_TO_FAILOVER'
 ```
 
 **Enable Load-balancing and streaming replication mode**
@@ -70,7 +70,7 @@ Health-checking and failover must be handled by EFM and hence, these must be dis
 
 ```text
 health_check_period = 0
-fail_over_on_backend_error = off
+failover_on_backend_error = off
 failover_if_affected_tuples_mismatch = off
 failover_command = ‘’
 failback_command = ‘’