[CAMEL-21581]: Remove ppc64le-specific maven profile for hashicorp-vault-starter #1333
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Jira: https://issues.apache.org/jira/browse/CAMEL-21581
Description:
Removed the ppc64le-specific Maven profile from the camel-hashicorp-vault-starter POM file to simplify the configuration and avoid hardcoding architecture-specific details.
Updated the camel-test-infra to dynamically retrieve the container image details from the [container.properties] file, ensuring a consistent and maintainable approach.
This change allows the appropriate container image to be selected based on the architecture without requiring separate profiles in the POM
Test Result:
ppc64le_hashicorp_starter_main_build_13.1image.txt
x86_hashicorp_starter_main_build_13.1image.txt