chore: bump Bifrost Helm chart to 2.1.23 with BigQuery/Kafka/PubSub plugins, multi-ingress support, extended Datadog config, and MCP pricing fields - #4336
Conversation
📝 WalkthroughWalkthroughBump Bifrost Helm chart to v2.1.23 (appVersion 1.5.12); add a 2.1.23 changelog and docs entry, update helm-charts index, expand Helm template validation test to include server.readBufferSize, and inline three OpenAPI 503 responses. ChangesBifrost Helm Chart Version 2.1.23 Release
Sequence Diagram(s)(silently skipped — changes are documentation, metadata, small script and OpenAPI inlines; no new multi-component runtime flow requiring a sequence diagram) Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 2 | ❌ 3❌ Failed checks (3 warnings)
✅ Passed checks (2 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Comment |
e53a982 to
b29a487
Compare
2dd7704 to
b55c0b0
Compare
b55c0b0 to
cc179a6
Compare
b29a487 to
311c3c3
Compare
chore: bump Bifrost Helm chart to 2.1.23 with BigQuery/Kafka/PubSub plugins, multi-ingress support, extended Datadog config, and MCP pricing fields
Confidence Score: 5/5Safe to merge — all changes are documentation, metadata, and CI test label updates with no runtime code touched. The diff consists entirely of version bump metadata, changelog prose, an OpenAPI spec cleanup, and a CI validation script fix. No Go code, Helm templates, or values schemas are modified in this PR; the actual template changes shipped on the base branch. The only minor inconsistency is the ConfigStoreUnavailable component being orphaned after inlining. The orphaned ConfigStoreUnavailable entry in docs/openapi/openapi.json is worth a quick cleanup pass, but poses no functional risk. Important Files Changed
Reviews (2): Last reviewed commit: "chore: helm release" | Re-trigger Greptile |
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@helm-charts/bifrost/README.md`:
- Line 14: Clarify whether pluginSpanFilter and otelPluginSpanFilter are the
same feature across releases: update the changelog entries so 2.1.23 explicitly
states that pluginSpanFilter is an expansion of the earlier OTEL-only
otelPluginSpanFilter (or state they are distinct and explain the difference);
reference the symbols pluginSpanFilter and otelPluginSpanFilter and the versions
2.1.23/2.1.22 in the single-line change summary to make the relationship
unambiguous.
- Around line 13-21: The README bullets are repetitive (many start with
"Added"); revise the entries to vary sentence starters and improve flow by using
different verbs and structures for each item—e.g., "Introduced
bifrost.governance.complexityAnalyzerConfig...", "Extended Datadog plugin to
include ml_app, dogstatsd_addr...", "Added support for bigquery plugin with
project_id, dataset_id...", "Reused $defs for pluginSpanFilter across
OTEL/Datadog/BigQuery...", "Added key_ids to virtual provider config (use
[\"*\"] for all keys)...", and "Introduced
bifrost.framework.pricing.mcpLibraryUrl and mcpLibrarySyncInterval...". Keep the
original technical details and symbols
(bifrost.governance.complexityAnalyzerConfig, pluginSpanFilter,
plugin_span_filter, bigquery, Datadog plugin fields, key_ids, kafka, pubsub,
bifrost.framework.pricing.mcpLibraryUrl) but vary verbs and sentence forms for
each bullet to improve readability.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: ASSERTIVE
Plan: Pro Plus
Run ID: ac6750c8-4d6c-48ef-9d6f-dd9f3a780101
📒 Files selected for processing (3)
helm-charts/bifrost/Chart.yamlhelm-charts/bifrost/README.mdhelm-charts/index.yaml
cc179a6 to
799d8e6
Compare
029162a to
cd685ae
Compare
cd685ae to
627741f
Compare
Merge activity
|
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@docs/changelogs/helm-v2.1.23.mdx`:
- Line 13: The changelog contains a typo: the word "defintion" in the entry
describing the new `bigquery` plugin should be corrected to "definition"; update
the text in `docs/changelogs/helm-v2.1.23.mdx` (the line listing the new
`bigquery` plugin fields) replacing `defintion` with `definition` so the
user-facing changelog reads "New `bigquery` plugin definition: …".
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: ASSERTIVE
Plan: Pro Plus
Run ID: fdc497af-5e47-4fcc-930f-f1a1031a7ca2
📒 Files selected for processing (7)
.github/workflows/scripts/validate-helm-templates.shdocs/changelogs/helm-v2.1.23.mdxdocs/docs.jsondocs/openapi/openapi.jsonhelm-charts/bifrost/Chart.yamlhelm-charts/bifrost/README.mdhelm-charts/index.yaml
💤 Files with no reviewable changes (3)
- helm-charts/bifrost/Chart.yaml
- helm-charts/index.yaml
- helm-charts/bifrost/README.md
| - Introduced `bifrost.governance.complexityAnalyzerConfig` for complexity router boundaries/keywords; renders into `governance.complexity_analyzer_config`. | ||
| - `pluginSpanFilter` (`mode`/`plugins`) is now supported in OTEL config (single- and multi-profile), with a shared `$defs` definition reused across OTEL, Datadog, and BigQuery connectors. | ||
| - Brought `plugin_span_filter` support to the Datadog plugin config. | ||
| - New `bigquery` plugin defintion: `project_id`, `dataset_id`, `table_id`, `location`, `service_account_key`, `create_table_if_not_exists`, `flush_interval_seconds`, `buffer_size`, `custom_labels`, `disable_content_logging`, `request_headers`, `plugin_span_filter`. |
There was a problem hiding this comment.
Fix the typo in plugin description.
Line 13 has defintion; this should be definition in user-facing changelog text.
Suggested patch
-- New `bigquery` plugin defintion: `project_id`, `dataset_id`, `table_id`, `location`, `service_account_key`, `create_table_if_not_exists`, `flush_interval_seconds`, `buffer_size`, `custom_labels`, `disable_content_logging`, `request_headers`, `plugin_span_filter`.
+- New `bigquery` plugin definition: `project_id`, `dataset_id`, `table_id`, `location`, `service_account_key`, `create_table_if_not_exists`, `flush_interval_seconds`, `buffer_size`, `custom_labels`, `disable_content_logging`, `request_headers`, `plugin_span_filter`.📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| - New `bigquery` plugin defintion: `project_id`, `dataset_id`, `table_id`, `location`, `service_account_key`, `create_table_if_not_exists`, `flush_interval_seconds`, `buffer_size`, `custom_labels`, `disable_content_logging`, `request_headers`, `plugin_span_filter`. | |
| - New `bigquery` plugin definition: `project_id`, `dataset_id`, `table_id`, `location`, `service_account_key`, `create_table_if_not_exists`, `flush_interval_seconds`, `buffer_size`, `custom_labels`, `disable_content_logging`, `request_headers`, `plugin_span_filter`. |
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@docs/changelogs/helm-v2.1.23.mdx` at line 13, The changelog contains a typo:
the word "defintion" in the entry describing the new `bigquery` plugin should be
corrected to "definition"; update the text in `docs/changelogs/helm-v2.1.23.mdx`
(the line listing the new `bigquery` plugin fields) replacing `defintion` with
`definition` so the user-facing changelog reads "New `bigquery` plugin
definition: …".

Summary
Briefly explain the purpose of this PR and the problem it solves.
Changes
Type of change
Affected areas
How to test
Describe the steps to validate this change. Include commands and expected outcomes.
If adding new configs or environment variables, document them here.
Screenshots/Recordings
If UI changes, add before/after screenshots or short clips.
Breaking changes
If yes, describe impact and migration instructions.
Related issues
Link related issues and discussions. Example: Closes #123
Security considerations
Note any security implications (auth, secrets, PII, sandboxing, etc.).
Checklist
docs/contributing/README.mdand followed the guidelinesSummary by CodeRabbit
New Features
Chores
Documentation
Tests