Configure all container image names in a one place #46504
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Centralize Container Image Configuration
Description
This PR addresses issue #45746, which aims to make container image configuration more maintainable by centralizing all image references in one place. Currently, image references are scattered across pom.xml files and Java source files, making it difficult to change image sources (e.g., switching from Docker Hub to Quay.io).
Implementation
ContainerImagesConfig
interface using@ConfigMapping
to provide type-safe access to container image namesNote: Not yet completed