chore: restructure guardrails values.yaml to list providers before rules with expanded inline examples and provider_config_ids linkage

[BearTS]

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

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 0fbd4d89-de9e-445b-9c87-bd9082c257b6

📥 Commits

Reviewing files that changed from the base of the PR and between 5be6515 and 45d181b.

📒 Files selected for processing (1)

• helm-charts/bifrost/values.yaml

Limit details: You’ve used all 4 included reviews currently available. Your 64 included PR review attempts over the past 7 days set your current allowance at 4 reviews per hour.

---

📝 Walkthrough

Summary by CodeRabbit

• Documentation
  • Updated guardrails examples with Grayswan provider configuration and an Anthropic/OpenAI content-safety rule.
  • Revised Azure provider examples to use models and aliases.
  • Added separate PostgreSQL configuration guidance for the logs store.
  • Documented PostgreSQL pod scheduling options, including node selectors, tolerations, and affinity.

Walkthrough

The Helm chart values update guardrails examples, external PostgreSQL configuration documentation, and PostgreSQL pod scheduling settings.

Changes

Helm values configuration

Layer / File(s)	Summary
Provider and rule examples helm-charts/bifrost/values.yaml	The examples define Grayswan provider settings and an Anthropic/OpenAI rule. The rule covers input and output, limits history to eight turns, sets a 15-second timeout, and references provider configuration ID 1.
External PostgreSQL and pod scheduling settings helm-charts/bifrost/values.yaml	The documentation adds external PostgreSQL credentials, TLS, password commands, and secret references. PostgreSQL pod values add nodeSelector, tolerations, and affinity settings.

Estimated code review effort: 1 (Trivial) | ~5 minutes

Merge Risk: ⚪ Minimal · up to 45d18

This change reorganizes and documents Helm guardrail configuration examples without introducing an actionable merge-blocking risk; it is merge-ready after normal checks and review.

Suggested reviewers: akshaydeo, roroghost17

🚥 Pre-merge checks | ✅ 2 | ❌ 3

❌ Failed checks (3 warnings)

Check name	Status	Explanation	Resolution
Linked Issues check	⚠️ Warning	The linked issue requires File API support for providers such as OpenAI and Anthropic, including file upload support. The PR changes Helm value documentation and examples only and does not implement F…	Implement the File API support required by issue #123, including the relevant provider integrations and file upload endpoint behavior, or link this PR to an issue that matches the Helm chart documentation changes.
Out of Scope Changes check	⚠️ Warning	The PR changes guardrails, Azure provider examples, logs-store PostgreSQL documentation, and PostgreSQL pod scheduling settings. These changes are unrelated to the linked issue's File API support requ…	Remove the unrelated Helm chart documentation and scheduling changes from this PR, or update the linked issues to include the corresponding chart configuration objectives.
Description check	⚠️ Warning	The description contains only the unfilled repository template. It does not explain the PR purpose, actual changes, affected areas, testing steps, breaking changes, security considerations, or checkli…	Replace the default placeholder text with completed sections that describe the Helm documentation changes, affected area, validation steps such as Helm lint or template rendering, breaking-change status, security considerations, and checkli…

✅ Passed checks (2 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Title check	✅ Passed	The title describes a real guardrails documentation change, but it does not cover the Azure examples, logs-store documentation, or PostgreSQL scheduling settings. It remains sufficiently related to th…

Full details: Linked Issues check

Explanation

The linked issue requires File API support for providers such as OpenAI and Anthropic, including file upload support. The PR changes Helm value documentation and examples only and does not implement File API functionality [#123].

Full details: Out of Scope Changes check

Explanation

The PR changes guardrails, Azure provider examples, logs-store PostgreSQL documentation, and PostgreSQL pod scheduling settings. These changes are unrelated to the linked issue's File API support requirements [#123].

Full details: Docstring Coverage

Explanation

No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (1 skipped: 1 unsupported.)

Full details: Title check

Explanation

The title describes a real guardrails documentation change, but it does not cover the Azure examples, logs-store documentation, or PostgreSQL scheduling settings. It remains sufficiently related to the changeset.

Full details: Description check

Explanation

The description contains only the unfilled repository template. It does not explain the PR purpose, actual changes, affected areas, testing steps, breaking changes, security considerations, or checklist status.

Resolution

Replace the default placeholder text with completed sections that describe the Helm documentation changes, affected area, validation steps such as Helm lint or template rendering, breaking-change status, security considerations, and checklist results.

• Fix all pre-merge checks with AI

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch 08-25-chore_guardrails_example_update_in_values.yaml

---

_{Comment @coderabbitai help to get the list of available commands.}

[BearTS]

• docs: add max_turns_to_send and evaluation_mode rule fields, move sampling_rate to rule level #6520
• chore: inherit semantic cache embedding keys from bifrost.providers and drop keys field from semantic cache config across Helm charts, values, and docs #6517
• chore: add metrics_enabled boolean to Bifrost Helm chart metrics schema and values #6513
• chore: restructure guardrails values.yaml to list providers before rules with expanded inline examples and provider_config_ids linkage #6512 👈 (View in Graphite)
• chore: remove deployments field from Azure/Vertex schema and replace with models/aliases in values.yaml comments #6510
• chore: condense values.yaml comments for clarity and brevity #6509
• feat(helm): support for external PostgreSQL support for logs store in helm #6226
• dev

This stack of pull requests is managed by Graphite. Learn more about stacking.

[Pratham-Mishra04]

Merge activity

• Aug 26, 5:43 AM UTC: A user started a stack merge that includes this pull request via Graphite.
• Aug 26, 5:53 AM UTC: Graphite rebased this pull request as part of a merge.
• Aug 26, 5:54 AM UTC: @Pratham-Mishra04 merged this pull request with Graphite.

The base branch was changed.