postgres/ci_scripts/setup-keyring-servers.sh

#!/bin/bash

set -e

SCRIPT_DIR="$(cd -- "$(dirname "$0")" >/dev/null 2>&1; pwd -P)"

cd /tmp

wget https://raw.githubusercontent.com/OpenKMIP/PyKMIP/refs/heads/master/bin/create_certificates.py
python3 create_certificates.py

mkdir policies
cd policies
wget https://raw.githubusercontent.com/OpenKMIP/PyKMIP/refs/heads/master/examples/policy.json
cd ..

echo $SCRIPT_DIR
rm -f /tmp/pykmip.db
pykmip-server -f "$SCRIPT_DIR/../contrib/pg_tde/pykmip-server.conf" -l /tmp/kmip-server.log &

CLUSTER_INFO=$(mktemp)
vault server -dev -dev-tls -dev-cluster-json="$CLUSTER_INFO" > /dev/null &
sleep 10
export VAULT_ROOT_TOKEN_FILE=$(mktemp)
jq -r .root_token "$CLUSTER_INFO" > "$VAULT_ROOT_TOKEN_FILE"
export VAULT_CACERT_FILE=$(jq -r .ca_cert_path "$CLUSTER_INFO")
rm "$CLUSTER_INFO"

## We need to enable key/value version 1 engine for just for tests
vault secrets enable -ca-cert="$VAULT_CACERT_FILE" -path=kv-v1 -version=1 kv

if [ -v GITHUB_ACTIONS ]; then
    echo "VAULT_ROOT_TOKEN_FILE=$VAULT_ROOT_TOKEN_FILE" >> $GITHUB_ENV
    echo "VAULT_CACERT_FILE=$VAULT_CACERT_FILE" >> $GITHUB_ENV
fi
CI updata 1: percona server for postgresql basic build and test This action is similar to what we had before, executin tests on Ubuntu 22.04 with both meson and make, all tests passing. The test is refactored to easily support other configurations, but those are not part of this commit yet because of failures. Oters will be added in separate commits with required script/code changes. The commit also contains a compilation / possibly bug fix reported by newer GCC versions 8 months ago			`#!/bin/bash`

Consistently use set -e in all our scripts It recently hid a bug in the code coverage job. 4 months ago			`set -e`

Make whitespace of CI scripts consistent 7 months ago			`SCRIPT_DIR="$(cd -- "$(dirname "$0")" >/dev/null 2>&1; pwd -P)"`
CI updata 1: percona server for postgresql basic build and test This action is similar to what we had before, executin tests on Ubuntu 22.04 with both meson and make, all tests passing. The test is refactored to easily support other configurations, but those are not part of this commit yet because of failures. Oters will be added in separate commits with required script/code changes. The commit also contains a compilation / possibly bug fix reported by newer GCC versions 8 months ago
			`cd /tmp`

			`wget https://raw.githubusercontent.com/OpenKMIP/PyKMIP/refs/heads/master/bin/create_certificates.py`
			`python3 create_certificates.py`

			`mkdir policies`
			`cd policies`
			`wget https://raw.githubusercontent.com/OpenKMIP/PyKMIP/refs/heads/master/examples/policy.json`
			`cd ..`

			`echo $SCRIPT_DIR`
Remove key provider files in regress tests To ensure the tests are always run from the same state we remove any key provider files so that pg_tde_add_database/global_key_provider_file() always creates a new file. 3 months ago			`rm -f /tmp/pykmip.db`
CI updata 1: percona server for postgresql basic build and test This action is similar to what we had before, executin tests on Ubuntu 22.04 with both meson and make, all tests passing. The test is refactored to easily support other configurations, but those are not part of this commit yet because of failures. Oters will be added in separate commits with required script/code changes. The commit also contains a compilation / possibly bug fix reported by newer GCC versions 8 months ago			`pykmip-server -f "$SCRIPT_DIR/../contrib/pg_tde/pykmip-server.conf" -l /tmp/kmip-server.log &`

PG-1607 Run our test suite for Vault with HTTPS Since the dev mode of Vault supports generating HTTPs ceritficates we should just use that since in production everyone will use HTTPS we should run our tests with HTTPS too. 4 months ago			`CLUSTER_INFO=$(mktemp)`
			`vault server -dev -dev-tls -dev-cluster-json="$CLUSTER_INFO" > /dev/null &`
CI updata 1: percona server for postgresql basic build and test This action is similar to what we had before, executin tests on Ubuntu 22.04 with both meson and make, all tests passing. The test is refactored to easily support other configurations, but those are not part of this commit yet because of failures. Oters will be added in separate commits with required script/code changes. The commit also contains a compilation / possibly bug fix reported by newer GCC versions 8 months ago			`sleep 10`
PG-1607 Run our test suite for Vault with HTTPS Since the dev mode of Vault supports generating HTTPs ceritficates we should just use that since in production everyone will use HTTPS we should run our tests with HTTPS too. 4 months ago			`export VAULT_ROOT_TOKEN_FILE=$(mktemp)`
			`jq -r .root_token "$CLUSTER_INFO" > "$VAULT_ROOT_TOKEN_FILE"`
			`export VAULT_CACERT_FILE=$(jq -r .ca_cert_path "$CLUSTER_INFO")`
			`rm "$CLUSTER_INFO"`
PG-1667 Validate vault key provider engine type pg_tde supports only Key/Value version 2 engine type for Hashicorp Vault. Add validation for that by quering mountpoint metadata. 2 months ago
			`## We need to enable key/value version 1 engine for just for tests`
			`vault secrets enable -ca-cert="$VAULT_CACERT_FILE" -path=kv-v1 -version=1 kv`

Remove support for external fields from key provider options 4 months ago			`if [ -v GITHUB_ACTIONS ]; then`
PG-1607 Run our test suite for Vault with HTTPS Since the dev mode of Vault supports generating HTTPs ceritficates we should just use that since in production everyone will use HTTPS we should run our tests with HTTPS too. 4 months ago			`echo "VAULT_ROOT_TOKEN_FILE=$VAULT_ROOT_TOKEN_FILE" >> $GITHUB_ENV`
			`echo "VAULT_CACERT_FILE=$VAULT_CACERT_FILE" >> $GITHUB_ENV`
Remove support for external fields from key provider options 4 months ago			`fi`