EAI_5857 fix CF version mismatch#233
Merged
woojae-siloai merged 1 commit intomainfrom Apr 29, 2026
Merged
Conversation
woojae-siloai
changed the title
oskarasbrink
approved these changes
Apr 28, 2026
This file contains hidden or 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
2 participants
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.
Summary
Fixes version mismatch where bloom ConfigMap showed hardcoded "2.0.0" instead of actual build version (e.g., "v2.0.4").
Root Cause
cmd.Version (set via build ldflags) was never passed to Ansible as BLOOM_VERSION, so it always defaulted to "2.0.0".
Solution
Added version parameter to runtime functions and injected BLOOM_VERSION following the existing BLOOM_DIR pattern.
Impact
6 lines changed (5 modified + 1 added). ConfigMap now shows correct build version instead of hardcoded "2.0.0".