Skip to content

Support system properties for Docker registries in Maven plugin #45253

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

Conversation

ryanjbaxter
Copy link

I would like to be able to configure Docker registry credentials in my global Maven settings.xml file. In order to do that we can introduce system properties for both the publish registry and builder registry.

@spring-projects-issues spring-projects-issues added the status: waiting-for-triage An issue we've not yet triaged label Apr 22, 2025
@wilkinsona wilkinsona added the for: team-meeting An issue we'd like to discuss as a team to make progress label Apr 22, 2025
@philwebb
Copy link
Member

Thanks for the PR @ryanjbaxter, but think with #45269 merged the extra properties are hopefully no longer necessary. I've tested things locally and no longer get the "Sign-in enforcement is enabled" message so hopefully the helper support will be enough.

@philwebb philwebb closed this Apr 25, 2025
@philwebb philwebb added status: superseded An issue that has been superseded by another and removed status: waiting-for-triage An issue we've not yet triaged for: team-meeting An issue we'd like to discuss as a team to make progress labels Apr 25, 2025
@ryanjbaxter
Copy link
Author

Thanks @philwebb. I tried 3.5.0-RC1 and it seemed to work without these properties set. Question though, does that mean these properties will eventually be removed in a future release?

@wilkinsona
Copy link
Member

This PR wasn't merged so the properties were never added.

@ryanjbaxter
Copy link
Author

Sorry I mean the configuration properties for DockerRegistrys (publisher and builder) that can be configured in the POM XML.

@wilkinsona
Copy link
Member

We don't plan to remove them. They remain an alternative when a credential helper's not being used. If the properties are configured in your pom they will take precedence over any credential helper that may be configured.

@ryanjbaxter
Copy link
Author

Wouldn't this PR still be useful the case where the credential helper is not being used so the properties can easily be externalized to the global maven settings.xml file?

@wilkinsona
Copy link
Member

We're trying to strike a balance here and we think that what we have now achieves that as we expect most users to have a credential helper configured. For those that don't, we believe the existing support is sufficient – the properties can still be externalized by using the already-documented approach. The extra properties proposed here add more complexity than we feel is justified for something that should now be a niche requirement.

@ryanjbaxter
Copy link
Author

OK thanks for the clarification @wilkinsona! We can always revisit this if we find there is a bigger demand for it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: superseded An issue that has been superseded by another
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants