Discuss improvements to cta-catalogue-updater container

There are some use-cases to improve the following cta-catalogue-updater features:

1) Support arbitrary git repo commits, for testing purposes

For the moment, the container only supports tagged versions of CTA. This means that we can only use the container for versions that have been released, and not versions that are under testing.

If this feature existed, it would have made it much easier to test the 10.0 to 11.0 catalogue migration.

Required work:

• We need to be able to pass any commit, maybe through a new script parameter. At the moment, it assumes that the version passed is a tagged version: https://gitlab.cern.ch/cta/eoscta-operations/containers/cta-catalogue-updater/-/blob/master/entrypoint.sh#L81
• If the version is not tagged, then the cta-catalogueutils RPM needs to be built and installed from the pulled repo. This can be an extra challenge : https://gitlab.cern.ch/cta/eoscta-operations/containers/cta-catalogue-updater/-/blob/master/entrypoint.sh#L73

2) Support postgres migrations

Recently, we have have received some requests to add liquibase migration scripts for postgres:

• CTA-old#1252 (closed)
• #112 (closed)

In order to be able to test future additions, we should be able to test postgres migrations with the container. At the moment it expects only oracle migrations, which causes it to fail.

Required work:

• Be able to switch off all Oracle dependencies and install the Postgres ones.