Skip to content

Conversation

meistermeier
Copy link
Contributor

This will not only update the test image but also clean up usage of withEnterpriseEdition to just append
the -enterprise suffix instead of pulling in the former neo4j:4.4 default image without users noting the implicit change from their defined image version.

This will not only update the test image but also clean up
usage of `withEnterpriseEdition` to just append
the `-enterprise` suffix instead of pulling in the former neo4j:4.4 default image
without users noting the implicit change from their defined image version.
@meistermeier meistermeier requested a review from a team as a code owner August 19, 2025 16:25
@@ -211,8 +206,7 @@ public Neo4jContainer withEnterpriseEdition() {
String.format("Cannot use enterprise version with alternative image %s.", getDockerImageName())
);
}

setDockerImageName(DEFAULT_IMAGE_NAME.withTag(ENTERPRISE_TAG).asCanonicalNameString());
setDockerImageName(DockerImageName.parse(getDockerImageName() + ENTERPRISE_SUFFIX).asCanonicalNameString());
Copy link
Member

Choose a reason for hiding this comment

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

this will break existing users. Why not improve the exception's message?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

From a technical, formal perspective I would say, that you are right.
But (of course) I would consider this as a bug that came as a left-over when we've removed the default constructor that fell back to the default image name.
I think that nobody would expect working with a neo4j:5.26 image to get ported back to the previous major version (4.4) when enabling enterprise per API.

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.

2 participants