keycloak-config-cli: fix bitnami symlink #44312
Merged
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
Signed-off-by: Michael Paul <[email protected]>
jamonation
approved these changes
Mar 3, 2025
octo-sts
bot
added
the
bincapz/pass
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.
The Bitnami keycloak-config-cli image defaults to the
bitnami - 1000:0user, however the defaults in their helm chart runs the container asbitnami - 1001:1001which throws an error about not being able to access the jarfile referenced by the current symlink.This fix changes the symlink to the full filepath and adjusts the subpackage test to confirm that this runs with the default Bitnami helm chart uid:gid.