Skip to content

Conversation

@AdheipSingh
Copy link
Contributor

@AdheipSingh AdheipSingh commented Dec 19, 2025

Fixes #1458.

Description


This PR has:

  • been tested to ensure log ingestion and log query works.
  • added comments explaining the "why" and the intent of the code wherever would not be obvious for an unfamiliar reader.
  • added documentation for new or modified features or behaviors.

Summary by CodeRabbit

  • Chores
    • Updated local mode secret configuration structure in deployment templates.

✏️ Tip: You can customize this high-level summary in your review settings.

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Dec 19, 2025

Walkthrough

The Helm template for the logstream job has been updated to iterate over .Values.parseable.localModeSecret.secrets instead of .Values.parseable.localModeSecret when generating environment variables from local secrets. The nested key iteration logic remains unchanged.

Changes

Cohort / File(s) Summary
Helm Template Configuration
helm/templates/logstream-job.yaml
Updated the local mode secret iteration source from .Values.parseable.localModeSecret to .Values.parseable.localModeSecret.secrets to correctly reference the nested secrets field when generating environment variables.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~5–10 minutes

  • Verify the change aligns with the expected YAML structure for local mode secrets in the values file
  • Confirm this mirrors the pattern used for s3ModeSecret (as referenced in related PR #1434)

Possibly related PRs

Suggested reviewers

  • nitisht

Poem

🐰 A little hop through YAML so neat,
Where secrets find their nested seat,
We fixed the path, now iterations flow,
Environment variables steal the show! ✨

Pre-merge checks and finishing touches

❌ Failed checks (1 inconclusive)
Check name Status Explanation Resolution
Description check ❓ Inconclusive The PR description references issue #1458 but lacks substantive details about the bug, solution, and key changes made to the Helm template. Provide a detailed description explaining what the logstream Helm template bug is, why the change from iterating over .Values.parseable.localModeSecret.secrets (instead of .Values.parseable.localModeSecret) fixes it, and confirm testing was completed.
✅ Passed checks (2 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly identifies the main change: fixing a Helm template bug in the logstream configuration by correcting how local secrets are iterated.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
✨ Finishing touches
  • 📝 Generate docstrings
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Helm template bug: Another issue with parseable/templates/logstream-job.yaml:51:37

1 participant