Design client tooling

[theory]

Design the tooling for clients. The goal is SDKs used to build and ship single binaries for each supported OS and architecture to support end user, developer, packaging, and CI/CD use case.

• [ ] Developer tools (Developer SDK)
  • Initialize projects
  • Manage metadata
  • Build and install for all supported platforms and pipelines
  • Run Tests on different Postgres versions
  • Bundle and Publish
  • Publish to private registry
• [ ] Packaging tools
  • Build and install for all supported platforms and pipelines
  • Run Tests on different Postgres versions
  • Package and Publish
• [ ] Installation/management tools (User SDK)
  • List extensions
  • Search extensions
  • Determine environment (Postgres version, OS, architecture)
  • Fetch the appropriate binary package for the configuration
  • Resolve and install all extension, system, and library dependencies
  • Install (or re-install) the package
  • Build from source for all supported pipelines
  • Validate an extension has been installed
  • Confirm successful installation
  • CREATE EXTENSION et al. in one or more databases
  • Use private registries as well as the Root Registry
  • Report on installed extensions and their status (used/not used, out of date)
• [ ] Compatibility (PGXN, Trunk, PGXMan, etc.)
• [ ] CI/CD Tools (overlaps with developer SDK)
  • Build and install for all supported platforms and pipelines
  • Run Tests on different Postgres versions
  • Bundle and Publish
  • Publish to private registry

[theory]

Initial sketch in pgxn/discussion#3.