Repository navigation
fix: add missing savings env vars to runtime-effects [OMN-7569] - #1164
Merged
Merged
Conversation
…569] PR #1161 added OMNIBASE_INFRA_SAVINGS_KAFKA_BOOTSTRAP_SERVERS and POSTGRES_HOST to runtime-worker but missed runtime-effects. The savings estimation consumer in runtime-effects fails on every startup with: ConfigSavingsEstimation validation error: kafka_bootstrap_servers Field required [type=missing] This is because ConfigSavingsEstimation uses env_prefix="OMNIBASE_INFRA_SAVINGS_" so the generic KAFKA_BOOTSTRAP_SERVERS is not picked up. Also updates service catalog YAMLs for both runtime-effects and runtime-worker to stay in sync with docker-compose.infra.yml.
jonahgabriel
enabled auto-merge
April 6, 2026 03:43
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (3)
📝 WalkthroughWalkthroughTwo environment variables ( Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
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
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
OMNIBASE_INFRA_SAVINGS_KAFKA_BOOTSTRAP_SERVERSandPOSTGRES_HOSTtoruntime-effectsindocker-compose.infra.ymlruntime-workerbut missedruntime-effects, which also runs the savings estimation consumerruntime-effectsandruntime-workerto stay in sync with composeRoot Cause
ConfigSavingsEstimationusesenv_prefix="OMNIBASE_INFRA_SAVINGS_", so the genericKAFKA_BOOTSTRAP_SERVERS=redpanda:9092(fromx-runtime-env) is not picked up. The savings consumer fails on every startup attempt with a Pydantic validation error:This results in
savings_estimatestable staying at 0 rows in omnidash_analytics.Test plan
infra-up-runtimedocker exec omninode-runtime-effects env | grep SAVINGSshows the new vardocker logs omninode-runtime-effectsno longer shows ConfigSavingsEstimation errorssavings_estimatestable for new rows after cost events flowSummary by CodeRabbit