Closed NyakudyaA closed 4 weeks ago
Currently the workflows allow publishing the following image tags
kartoza/postgis:17-3.5--v2024.10.20
kartoza/postgis:17-3.5
kartoza/postgis:latest
Each time a PR is merged, we are always updating the kartoza/postgis:17-3.5 image, this is not ideal especially for people who use these in production
We need to adjust the action to be able to do the following
Publish the following tags and updates
When a PR is merged we need to check if kartoza/postgis:17-3.5 already exists, if so we skip updating it but only update the following
Only the kartoza/postgis:17-3.5 - should be updated only if there is a bug or any security updates
Feature description
Currently the workflows allow publishing the following image tags
kartoza/postgis:17-3.5--v2024.10.20> with the last date being the date the image is pushedkartoza/postgis:17-3.5- Latest versionkartoza/postgis:latest- We tag the latestEach time a PR is merged, we are always updating the
kartoza/postgis:17-3.5image, this is not ideal especially for people who use these in productionAdditional context
Solution
We need to adjust the action to be able to do the following
Publish the following tags and updates
New version of postgis
kartoza/postgis:17-3.5--v2024.10.20> with the last date being the date the image is pushedkartoza/postgis:17-3.5- Latest versionkartoza/postgis:latest- We tag the latestUpdate of existing tag i.e 17-3.5
When a PR is merged we need to check if kartoza/postgis:17-3.5 already exists, if so we skip updating it but only update the following
kartoza/postgis:17-3.5--v2024.10.20> with the last date being the date the image is pushedkartoza/postgis:latest- We tag the latestOnly the
kartoza/postgis:17-3.5- should be updated only if there is a bug or any security updates