Updated license.md file

.github/workflows/run_unit_tests_on_docker.yml

@@ -0,0 +1,74 @@
+name: Docker tests
+run-name: ${{ github.actor }} is running the test schedules.
+on:
+  push:
+
+  pull_request:
+
+
+jobs:
+  run-scripts:
+    strategy:
+      fail-fast: false
+      matrix:
+        os: [ubuntu-22.04]
+        pgver: [14, 15, 16, 17]
+
+    runs-on: ${{ matrix.os }}
+
+    steps:
+    - name: Checkout cli
+      uses: actions/checkout@v4
+      with:
+        ref: ${{ github.ref }}
+
+    - name: Set up Docker
+      uses: docker/setup-buildx-action@v2
+
+    - name: Build Docker Image
+      run: |
+        docker build --build-arg PGVER=${{ matrix.pgver }} -t cli .
+
+    - name: Run Docker Container
+      run: |
+        docker run -d --name cli -e POSTGRES_HOST_AUTH_METHOD=trust -p 5432:5432 cli
+
+
+    - name: Wait for PostgreSQL to be ready
+      run: |
+        echo "Waiting for Postgres to be ready..."
+        for i in {1..30}; do
+          if pg_isready -h localhost -p 5432 -U postgres; then
+            echo "PostgreSQL is ready!"
+              exit 0
+          fi
+          echo "PostgreSQL is not ready yet. Retrying in 5 seconds..."
+          sleep 5
+          done
+          echo "PostgreSQL did not become ready in time. Exiting."
+          exit 1
+
+    - name: Set up Python
+      uses: actions/setup-python@v4
+      with:
+        python-version: '3.10'
+
+    - name: Install dependencies
+      run: |
+        sudo apt -y update
+        sudo apt install -y postgresql-client \
+            libpq-dev \
+            python3-dev \
+            python3-psycopg2 \
+            python3-dotenv
+
+    - name: Run Test Harness (runner.py)
+      run: |
+        python test/runner.py -c test/t/lib/${{ matrix.pgver }}config.env -s test/schedule_files/script_file -k
+        cat latest.log
+
+    - name: Upload Log File as Artifact
+      uses: actions/upload-artifact@v4
+      with:
+        name: latest-log-${{ matrix.pgver }}
+        path: latest.log

.gitignore

@@ -1,4 +1,5 @@
 *.pyc
+*.orig
 out/
 devel/pg/src
 devel/pg/1*

Dockerfile

@@ -0,0 +1,23 @@
+ARG PGVER
+FROM postgres:$PGVER-alpine
+
+RUN apk add --no-cache \
+    make \
+    gcc \
+    musl-dev \
+    postgresql-dev \
+    git \
+    clang \
+    llvm
+
+WORKDIR /home/postgres/snowflake
+
+COPY . /home/postgres/snowflake/
+
+#RUN USE_PGXS=1 make && USE_PGXS=1 make install
+
+EXPOSE 5432
+
+ENTRYPOINT ["docker-entrypoint.sh"]
+
+CMD ["postgres"]

LICENSE.md

@@ -1,3 +1,9 @@
+-------------------------------------------------------------------------
+
+  Copyright (c) 2025, pgEdge, Inc.
+
+--------------------------------------------------------------------------
+
 ## pgEdge Community License Agreement 1.1
 
 This pgEdge Community License Agreement Version 1.1 (the "**Agreement**") sets forth the terms on which pgEdge, Inc. ("**pgEdge**") makes available certain software made available by pgEdge under this Agreement (the "**Software**"). BY INSTALLING, DOWNLOADING, ACCESSING, USING OR DISTRIBUTING ANY OF THE SOFTWARE, YOU AGREE TO THE TERMS AND CONDITIONS OF THIS AGREEMENT. IF YOU DO NOT AGREE TO SUCH TERMS AND CONDITIONS, YOU MUST NOT USE THE SOFTWARE. IF YOU ARE RECEIVING THE SOFTWARE ON BEHALF OF A LEGAL ENTITY, YOU REPRESENT AND WARRANT THAT YOU HAVE THE ACTUAL AUTHORITY TO AGREE TO THE TERMS AND CONDITIONS OF THIS AGREEMENT ON BEHALF OF SUCH ENTITY. "**Licensee**" means you, an individual, or the entity on whose behalf you are receiving the Software.

README.md

@@ -1,26 +1,75 @@
-# The CLI for pgEdge
+# The Command Line Interface (CLI)
 
-This is the pgEdge Command Line Interface (CLI) for managing components. 
-Take a look at our main pgEdge [repo](https://github.com/pgEdge/pgedge) for tips and example CLI commands.
+This is the Command Line Interface (CLI) for managing components. 
 
-You can also peruse our [CHANGELOG](https://github.com/pgEdge/pgedge/blob/main/CHANGELOG.md) if you'd like to learn more about our recent enhancements and fixes.
+## Table of Contents
+- [Creating a Development Environment](README.md#creating-a-development-environment)
+- [CLI Functions](docs/cli_functions.md)
+- [Tutorials](docs/tutorials.md)
+- [Release Notes](docs/cli_release_notes.md)
 
-# Using the CLI to control a pgEdge cluster
+### Prerequisites
 
-Get started quickly by taking a look at our [tutorials](https://github.com/pgEdge/pgedge/tree/main/cli/tutorials) to create your own localhost or vm cluster.
+On each machine that will host a replication node, you must:
 
-Check out our [commands](https://github.com/pgEdge/pgedge/tree/main?tab=readme-ov-file#cli-commands) to learn more about our multi-master power at your fingertips. :-)
+* Open any firewalls that could obstruct access between your servers.
+* Set SELinux to `permissive` or `disabled` mode on each host, followed by a system reboot.
+* Configure [passwordless sudo access](#configuring-passwordless-sudo) for a non-root OS user on each host.
+* Configure [passwordless ssh](#configuring-passwordless-ssh) access for the same non-root OS user on each host.
 
+### Creating a Development Environment
+After meeting the prerequisites:
 
-# To setup a dev environment:
+1.) Clone this repository.
 
-1.) Clone this repo
+2.) Move into the setup directory: `cd cli/devel/setup`
 
-2.) cd cli/devel/setup
+3.) Run the setup scripts: `./10-toolset.sh` through `30-bashrc.sh`
 
-3.) run `./1-cli.sh`
+4.) Source the `~/.bashrc` file.
 
-4.) configure your ~/.aws/config credentials
+5.) Run `40-awscli.sh` to install AWS in a virtual environment.
 
-5.) run `1d-pull-IN.sh` to retrieve REPO files
+6.) Configure your `~/.aws/config` credentials.
 
+7.) Run `50-pull-IN.sh` to retrieve the REPO files.
+
+### Using the CLI
+
+When using the CLI, you should ensure that you:
+
+**Include a Primary Key in Each Table** 
+
+All tables must include a primary key; this allows pgEdge to replicate `INSERT`, `UPDATE`, and `DELETE` statements. If your table does not include a primary key, only `INSERT` statements will be replicated to the table.
+
+**Use Snowflake Sequences instead of PostgreSQL sequences** 
+
+If you use a PostgreSQL sequence as part of your primary key, you should convert your sequences to [Snowflake sequences](https://github.com/pgEdge/snowflake). Snowflake sequences are composed of multiple data types that ensure a unique transaction sequence when processing your data in multiple regions. This helps  accurately preserve the order in which globally distributed transactions are performed, and alleviates concerns that network lag could disrupt sequences in distributed transactions.
+
+**Include the ENABLE ALWAYS clause in Triggers** 
+
+PostgreSQL triggers will fire only from the node on which they were invoked. If you have triggers that are related to the replication process, you should include the `ENABLE ALWAYS` clause when attaching a trigger to a table:
+
+```
+CREATE TRIGGER ins_trig AFTER INSERT ON my_table FOR EACH ROW EXECUTE PROCEDURE ins_history();
+ALTER TABLE trans_history ENABLE ALWAYS TRIGGER ins_trig;
+```
+
+#### Configuring Passwordless SSH
+
+You can use the following steps to configure passwordless SSH on each node of the replication cluster:
+
+```sh
+ssh-keygen -t rsa
+cd ~/.ssh
+cat id_rsa.pub >> authorized_keys
+chmod 700 ~/.ssh && chmod 600 ~/.ssh/authorized_keys
+```
+
+#### Configuring Passwordless sudo
+
+To configure passwordless sudo, open the /etc/sudoers file, and add a line of the form:
+
+%username         ALL = (ALL) NOPASSWD: ALL
+
+Where `username` specifies the name of your operating system user.

bp.sh

@@ -22,8 +22,15 @@ if [ -d $outp ]; then
 fi
 
 ./devel/startHTTP.sh
-./build.sh -X posix -R
 
+echo "Waiting for Python HTTP server to start..."
+while ! nc -z localhost 8000; do
+  sleep 1  # Check every second
+done
+
+echo "HTTP server is up!"
+
+./build.sh -X posix -R
 cd $outp
 
 ./$api set GLOBAL REPO http://localhost:8000

build.sh

@@ -340,7 +340,6 @@ initPG () {
     initC "lolor-pg$pgM"      "lolor"      "$lolorV"     "$outPlat" "postgres/lolor"     "" "" "nil"
     initC "snowflake-pg$pgM"  "snowflake"  "$snwflkV"    "$outPlat" "postgres/snowflake" "" "" "nil"
     initC "spock40-pg$pgM"    "spock40"    "$spock40V"   "$outPlat" "postgres/spock40"   "" "" "nil"
-    initC "spock40-pg$pgM"    "spock40"    "$spock40V1"  "$outPlat" "postgres/spock40"   "" "" "nil"
   fi
 
   if [ "$pgM" \> "13" ] && [ "$pgM" \< "17" ]; then

cli/scripts/ConsoleLogger.py

@@ -1,5 +1,5 @@
 
-#  Copyright 2022-2024 PGEDGE  All rights reserved. #
+#  Copyright 2022-2025 PGEDGE  All rights reserved. #
 
 import os
 import sys

cli/scripts/ace-tests/.coveragerc

@@ -0,0 +1,14 @@
+[run]
+source = hub/scripts
+omit = 
+    */tests/*
+    */__init__.py
+    */ace-tests/*
+
+[report]
+exclude_lines =
+    pragma: no cover
+    def __repr__
+    raise NotImplementedError
+    if __name__ == .__main__.:
+    pass