PostgreSQL-Open-Automation-Framework

An open framework for provisioning the infrastructure and (eventually) configuring the software stack behind a PostgreSQL deployment, across the major public clouds.

The current scope is VM provisioning + Ansible inventory generation. Downstream Ansible playbooks consume the generated inventory to install and configure PostgreSQL on the provisioned fleet.

Layout

terraform/                  # Multi-cloud VM provisioner
├── clouds/{gcp,aws,azure}/ # One Terraform root per cloud
├── modules/                # Reusable cloud + inventory modules
├── doc/                    # Per-cloud setup guides
└── scripts/validate.sh     # fmt / init / validate across all roots

ansible/                    # Percona PostgreSQL + Patroni + etcd configurator
├── inventory/{gcp,aws,azure}/  # Populated from terraform/ via scripts/sync-inventory.sh
├── roles/                  # common, storage, pg_repos, postgresql, etcd, patroni, …
├── playbooks/              # site.yml + phased + day-2 ops
└── doc/                    # User-facing docs (README, handoff contract, runbook)

Each cloud is an independent Terraform root — you only need credentials for the cloud whose directory you are working in. State files do not cross providers. Ansible consumes the inventory + credentials Terraform emits; it never reads Terraform state directly. See ansible/doc/handoff.md for the full contract.

Getting started

1. Pick a cloud (gcp, aws, or azure) and read the matching guide in terraform/doc/.
2. cd terraform/clouds/<cloud>/ and copy terraform.tfvars.example to terraform.tfvars. Fill in your project / region / SSH key paths.
3. terraform init && terraform validate && terraform plan -out=tfplan
4. terraform apply tfplan — on success ansible_inventory.yml, ansible_inventory.ini, and a sensitive credentials.json are written next to the cloud root.

See terraform/doc/README.md for the index of per-provider guides, and ansible/doc/README.md for the Ansible layer.

Status

This is an early, in-development project.

• Terraform layer: functional across GCP, AWS and Azure. Renders both YAML (primary) and INI (compat) Ansible inventory plus a sensitive credentials.json sidecar after every terraform apply.
• Ansible layer: design and documentation are published (ansible/doc/). Roles and playbooks are not yet implemented — contributions welcome.

License

To be determined — open the issues tab to discuss.