Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Migrate postgis image to the postgis/postgis docker hub repo. #2797

Merged
merged 2 commits into from
Jun 4, 2020

Conversation

azapasnik
Copy link
Contributor

Hello all. mdillon/postigs image was renamed to postgis/postgis few months ago. the discussion. Since that time the image has been updated with new postgres and postgis versions.

I've updated the image name and default version but there is a concern with the tags. Migration to the new image broke tag names backward compatibility with the old one.
Since the new postgis version was added to the repo the image tags were changes. I.e mdillon/postgis:10 became postgis/postgis:10-2.5.

Copy link
Member

@kiview kiview left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the PR and the background info about the Docker Hub renaming. I wonder if we have any chance to more gracefully handle the breaking change.

As it seems, the new tag format contains a -, so would it be sensible to check for this in the configure step and log an error, informing the user about the migration? Or is it enough to mention this breaking change in the changelog?

cc @rnorth @bsideup

@kiview
Copy link
Member

kiview commented May 29, 2020

Hey @Sanych, because of the breaking nature of this PR, we plan to pull it in for version 1.15.0. Thanks for your efforts.

@azapasnik
Copy link
Contributor Author

Hey. Are there any thoughts when 1.15 version is expected?

@kiview kiview added this to the next milestone Jun 4, 2020
@kiview kiview merged commit e94e13e into testcontainers:master Jun 4, 2020
@kiview
Copy link
Member

kiview commented Jun 4, 2020

Hi @Sanych, since 1.15 will be the next release, I just merged the PR. You can expect a release "soon" 🙂

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants