Skip to content

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

Merged
akshaydeo merged 5 commits into
devfrom
06-12-chore_helm_release
Jun 12, 2026
Merged

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
akshaydeo merged 5 commits into
devfrom
06-12-chore_helm_release

Conversation

@BearTS

@BearTS BearTS commented Jun 12, 2026

Copy link
Copy Markdown
Contributor

Summary

Briefly explain the purpose of this PR and the problem it solves.

Changes

  • What was changed and why
  • Any notable design decisions or trade-offs

Type of change

  • Bug fix
  • Feature
  • Refactor
  • Documentation
  • Chore/CI

Affected areas

  • Core (Go)
  • Transports (HTTP)
  • Providers/Integrations
  • Plugins
  • UI (React)
  • Docs

How to test

Describe the steps to validate this change. Include commands and expected outcomes.

# Core/Transports
go version
go test ./...

# UI
cd ui
pnpm i || npm i
pnpm test || npm test
pnpm build || npm run build

If adding new configs or environment variables, document them here.

Screenshots/Recordings

If UI changes, add before/after screenshots or short clips.

Breaking changes

  • Yes
  • No

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

  • I read docs/contributing/README.md and followed the guidelines
  • I added/updated tests where appropriate
  • I updated documentation where needed
  • I verified builds succeed (Go and UI)
  • I verified the CI pipeline passes locally if applicable

Summary by CodeRabbit

  • New Features

    • Complexity analyzer configuration
    • OTEL and Datadog plugin span filtering
    • BigQuery, Kafka, and Pub/Sub plugin additions/enhancements
    • MCP pricing catalog options
    • Nested virtual-provider key ID support
    • Multi-ingress resource generation from named maps
    • Configurable HTTP server read buffer size
  • Chores

    • Helm chart bumped to 2.1.23 (app version 1.5.12); chart index updated
  • Documentation

    • Updated changelog, README and site navigation; OpenAPI 503 responses clarified
  • Tests

    • Helm template validation updated to include new properties

@coderabbitai

coderabbitai Bot commented Jun 12, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

📝 Walkthrough

Walkthrough

Bump 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.

Changes

Bifrost Helm Chart Version 2.1.23 Release

Layer / File(s) Summary
Chart version and appVersion bump
helm-charts/bifrost/Chart.yaml
Chart version updated to 2.1.23; appVersion updated to 1.5.12.
Changelog pages and README update
docs/changelogs/helm-v2.1.23.mdx, helm-charts/bifrost/README.md, docs/docs.json
Add MDX changelog for v2.1.23, expand README changelog replacing the "Upcoming [2.1.23]" placeholder, trim duplicated 2.1.22 items, and register the new changelog page in docs.json.
Repository index entry and timestamp
helm-charts/index.yaml
Add new entries.bifrost release record for version: 2.1.23 with updated appVersion, created, digest, and urls; update top-level generated timestamp.
Helm template validation test update
.github/workflows/scripts/validate-helm-templates.sh
Expand the "combined" test label to Gap 1–9 and include bifrost.server.readBufferSize=131072 in the combined --set arguments.
OpenAPI 503 responses inlined
docs/openapi/openapi.json
Replace three $ref uses of ConfigStoreUnavailable with inline 503 response objects describing "Config store not available" and referencing #/components/schemas/BifrostError; adjust final file newline/brace.

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

  • danpiths
  • akshaydeo
  • Pratham-Mishra04

Poem

🐰 A tiny bump, a changelog bright,
Charts aligned in morning light,
Index updated, tests extended too,
Docs polished, JSON tidy and true,
Bifrost hops forward — v2.1.23, woo!

🚥 Pre-merge checks | ✅ 2 | ❌ 3

❌ Failed checks (3 warnings)

Check name Status Explanation Resolution
Description check ⚠️ Warning The PR description is entirely a template with no actual content filled in; all sections remain in template form with placeholders and unchecked boxes. Replace the template with actual summary of changes, type of change selection, testing steps, and completion of the contributor checklist.
Linked Issues check ⚠️ Warning The PR's changes involve Helm chart updates and documentation, but the linked issue #123 concerns Files API support for providers, which is unrelated to Helm chart versioning. Remove the unrelated linked issue #123 or provide correct linked issues that describe the Helm chart v2.1.23 release objectives.
Out of Scope Changes check ⚠️ Warning The PR includes multiple out-of-scope changes relative to the linked issue #123 (Files API Support). All changes involve Helm chart versioning, configuration documentation, and OpenAPI schema updates unrelated to Files API implementation. Either address the Files API implementation requirements from issue #123 or link the PR to appropriate Helm release-related issues.
✅ Passed checks (2 passed)
Check name Status Explanation
Title check ✅ Passed The PR title accurately summarizes the main change: bumping the Bifrost Helm chart to version 2.1.23 and lists the key features/additions included in this release.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
📝 Generate docstrings
  • Create stacked PR
  • Commit on current branch
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch 06-12-chore_helm_release

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

@BearTS
BearTS force-pushed the 06-12-chore_helm_release branch from e53a982 to b29a487 Compare June 12, 2026 10:22
@BearTS
BearTS force-pushed the 06-12-chore_public_helm_oci_registry branch from 2dd7704 to b55c0b0 Compare June 12, 2026 10:22
@BearTS
BearTS marked this pull request as ready for review June 12, 2026 10:36
@BearTS
BearTS requested a review from a team as a code owner June 12, 2026 10:36
@BearTS
BearTS force-pushed the 06-12-chore_public_helm_oci_registry branch from b55c0b0 to cc179a6 Compare June 12, 2026 10:36
@BearTS
BearTS force-pushed the 06-12-chore_helm_release branch from b29a487 to 311c3c3 Compare June 12, 2026 10:36
@BearTS BearTS changed the title chore: helm release chore: bump Bifrost Helm chart to 2.1.23 with BigQuery/Kafka/PubSub plugins, multi-ingress support, extended Datadog config, and MCP pricing fields Jun 12, 2026
@greptile-apps

greptile-apps Bot commented Jun 12, 2026

Copy link
Copy Markdown
Contributor

Confidence Score: 5/5

Safe 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

Filename Overview
.github/workflows/scripts/validate-helm-templates.sh Test label updated from "Gap 1-8" to "Gap 1-9" and bifrost.server.readBufferSize added to the combined test — correctly wires the new Gap 9 field into CI validation.
docs/changelogs/helm-v2.1.23.mdx New changelog page for v2.1.23, correctly registered in docs/docs.json. Contains a typo ("defintion") but is otherwise accurate.
docs/docs.json New changelog page changelogs/helm-v2.1.23 prepended to the Helm changelog list, maintaining reverse-chronological ordering.
docs/openapi/openapi.json Three 503 responses previously using $ref: #/components/responses/ConfigStoreUnavailable have been inlined. The ConfigStoreUnavailable component definition remains in components.responses but is now unreferenced (orphaned).
helm-charts/bifrost/Chart.yaml Version bumped from 2.1.22 → 2.1.23, appVersion from 1.5.9 → 1.5.12.
helm-charts/bifrost/README.md 2.1.23 "Upcoming" section promoted to released; several features drafted under 2.1.22 (BigQuery, Kafka, PubSub, Datadog plugin_span_filter) correctly moved to 2.1.23.
helm-charts/index.yaml New 2.1.23 index entry added with correct SHA-256 digest, download URL, and timestamps; generated timestamp updated.

Reviews (2): Last reviewed commit: "chore: helm release" | Re-trigger Greptile

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

📥 Commits

Reviewing files that changed from the base of the PR and between cc179a6 and 311c3c3.

📒 Files selected for processing (3)
  • helm-charts/bifrost/Chart.yaml
  • helm-charts/bifrost/README.md
  • helm-charts/index.yaml

Comment thread helm-charts/bifrost/README.md Outdated
Comment thread helm-charts/bifrost/README.md Outdated
@BearTS
BearTS force-pushed the 06-12-chore_public_helm_oci_registry branch from cc179a6 to 799d8e6 Compare June 12, 2026 10:42
@BearTS
BearTS force-pushed the 06-12-chore_helm_release branch 2 times, most recently from 029162a to cd685ae Compare June 12, 2026 10:44
@BearTS
BearTS force-pushed the 06-12-chore_helm_release branch from cd685ae to 627741f Compare June 12, 2026 10:48

akshaydeo commented Jun 12, 2026

Copy link
Copy Markdown
Contributor

Merge activity

  • Jun 12, 10:50 AM UTC: A user started a stack merge that includes this pull request via Graphite.
  • Jun 12, 10:54 AM UTC: @akshaydeo merged this pull request with Graphite.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

📥 Commits

Reviewing files that changed from the base of the PR and between 311c3c3 and 627741f.

📒 Files selected for processing (7)
  • .github/workflows/scripts/validate-helm-templates.sh
  • docs/changelogs/helm-v2.1.23.mdx
  • docs/docs.json
  • docs/openapi/openapi.json
  • helm-charts/bifrost/Chart.yaml
  • helm-charts/bifrost/README.md
  • helm-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`.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor | ⚡ Quick win

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.

Suggested change
- 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: …".

@akshaydeo
akshaydeo changed the base branch from 06-12-chore_public_helm_oci_registry to graphite-base/4336 June 12, 2026 10:53
@akshaydeo
akshaydeo changed the base branch from graphite-base/4336 to dev June 12, 2026 10:54
@akshaydeo
akshaydeo merged commit 60a6fb8 into dev Jun 12, 2026
11 checks passed
@akshaydeo
akshaydeo deleted the 06-12-chore_helm_release branch June 12, 2026 10:54
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.

Files API Support

2 participants