POC pushing & pulling trunk from an OSI registry #69
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Modify
trunk.mk
to build JSON files required to build OCI image manifests and an OCI image index, including newmake
variablesTITLE
,DESCRIPTION
,VENDOR
,URL
, andREPO_URL
.Add
push_trunk
, a shell script to take those JSON files and useoras
to build the images and manifests and push them to a registry.Add
docker_compose.yml
to spin up a PGXN tools image for AMD64 and running Postgres 16, as well as zot, a vendor-neutral OCI registry.Finally, modify
install_trunk
to download an artifact from a registry address, rather than build from a local file. Useoras
to fetch the image for the current platform. There's no support for distinguishing between artifacts built for different Postgres versions, but there are annotations in the image index that would allow it.