izgeri
commented
3 years ago Note that in the PRs that resolve this issue, we haven't fully addressed:
In the Conjur base image, we also need to determine a strategy for updating the postgres client that gets installed in the Conjur base images. At current, we pin the postgres version we use here: https://github.com/cyberark/conjur-base-image/blob/da1ca9d848d29f07e7bf20094005a7fbc00699f7/postgres-client-builder/build.sh#L5
We also test that the postgres version installed in the base images actually matches the pinned version. If our tests and deployment modes will pin only the postgres server major version, we will need a strategy to ensure the client continues to be compatible with the server version.
This is a much larger question, and discussions are happening offline for the right approach here. Follow-up issues will be filed once the approach is better understood.
Currently we have postgres pinned for Conjur OSS to 10.15. We'd like to pin instead to the major version so that our tests and deployment tools will automatically use the newest Postgres 10 version.
Developer Notes
The following images need to be updated to refer to
postgres:10:In the Conjur base image, we also need to determine a strategy for updating the postgres client that gets installed in the Conjur base images. At current, we pin the postgres version we use here: https://github.com/cyberark/conjur-base-image/blob/da1ca9d848d29f07e7bf20094005a7fbc00699f7/postgres-client-builder/build.sh#L5
We also test that the postgres version installed in the base images actually matches the pinned version. If our tests and deployment modes will pin only the postgres server major version, we will need a strategy to ensure the client continues to be compatible with the server version.