feat: add optional project_id field to Bedrock and Bedrock Mantle key configs

[impoiler]

Summary

Adds an optional project_id field to both BedrockKeyConfig and BedrockMantleKeyConfig, allowing users to scope Bedrock Mantle-routed models (OpenAI-family / Gemma) to a specific project via the OpenAI-Project / anthropic-workspace-id header. When left empty, the account's default project is used.

Changes

• Added project_id as an optional SecretVar field to BedrockKeyConfig and BedrockMantleKeyConfig types and their corresponding defaults.
• Extended the Zod validation schemas (bedrockKeyConfigSchema, bedrockMantleKeyConfigSchema, BedrockKeyConfigSchema, BedrockMantleKeyConfigSchema) to include the optional project_id field.
• Added UI form fields for project_id in both the Bedrock and Bedrock Mantle provider configuration sections, accepting a project ID or an environment variable reference (e.g., proj_xxxxxxxx or env.BEDROCK_PROJECT_ID).

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

1. Navigate to the Bedrock or Bedrock Mantle provider configuration in the workspace settings.
2. Verify the new Mantle Project ID (Optional) / Project ID (Optional) field appears in the form.
3. Enter a project ID (e.g., proj_xxxxxxxx) or an environment variable reference (e.g., env.BEDROCK_PROJECT_ID) and save.
4. Confirm the value is persisted and sent correctly when routing requests to Mantle-backed models.

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

Screenshots/Recordings

Add before/after screenshots of the Bedrock and Bedrock Mantle provider configuration forms showing the new Project ID field.

Breaking changes

• No

Related issues

Security considerations

The project_id field is handled as a SecretVar, consistent with other sensitive Bedrock configuration values, supporting both inline values and environment variable references.

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]

Caution

Review failed

The pull request is closed.

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 4a508b68-a09c-4df4-8142-5c446b17fd80

📥 Commits

Reviewing files that changed from the base of the PR and between fa238f8 and 4c1b66a.

📒 Files selected for processing (4)

• ui/app/workspace/providers/fragments/apiKeysFormFragment.tsx
• ui/lib/schemas/providerForm.ts
• ui/lib/types/config.ts
• ui/lib/types/schemas.ts

---

📝 Walkthrough

Summary by CodeRabbit

• New Features

  • Added optional Project ID fields to Bedrock and Bedrock Mantle provider credentials.
  • Project IDs support request scoping through provider-specific headers and environment-backed values.
  • Added input guidance and validation for Project ID formats.

• Documentation

  • Clarified when to enable Vertex’s “Force single region” setting for provisioned-throughput deployments.

Walkthrough

Bedrock and Bedrock Mantle key configurations now support optional project IDs across UI fields, validation schemas, TypeScript types, defaults, and secret-variable schemas. Vertex single-region guidance was also reworded.

Changes

Bedrock project ID configuration

Layer / File(s)	Summary
Project ID configuration contracts ui/lib/schemas/providerForm.ts, ui/lib/types/config.ts, ui/lib/types/schemas.ts	Bedrock and Bedrock Mantle schemas, interfaces, defaults, and secret-variable schemas now include optional project_id values. Empty request type formatting was also normalized.
Provider key form fields ui/app/workspace/providers/fragments/apiKeysFormFragment.tsx	Bedrock and Bedrock Mantle sections now render optional project ID inputs with descriptions, placeholders, and validation messages; Vertex single-region guidance was reformatted and expanded.

Estimated code review effort: 3 (Moderate) | ~20 minutes

Sequence Diagram(s)

sequenceDiagram
  participant SecretVarInput
  participant ProviderFormSchema
  participant BedrockKeyConfig
  SecretVarInput->>ProviderFormSchema: Submit optional project_id
  ProviderFormSchema->>BedrockKeyConfig: Validate project_id

Loading

Possibly related PRs

• maximhq/bifrost#4737: Adds related Bedrock Mantle project configuration in UI and schema areas.
• maximhq/bifrost#4886: Updates backend handling of BedrockMantleKeyConfig, connecting to this data-model change.

Suggested reviewers: akshaydeo, danpiths, roroghost17, tejasghatte

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Title check	✅ Passed	The title is concise and accurately describes the main change: adding optional project_id fields to Bedrock configs.
Description check	✅ Passed	The PR description covers summary, changes, testing, type, affected areas, breaking changes, security, and checklist; only related issues is empty.

✨ 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 07-13-feat_project_id_support_for_ui

---

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

[impoiler]

• feat: add BedrockMantleSection UI component and project_id override for Bedrock deployments #5142
• feat: add per-alias ProjectID override for Bedrock, Bedrock Mantle, and Vertex providers #5141
• feat: add optional project_id field to Bedrock and Bedrock Mantle key configs #5134 👈 (View in Graphite)
• feat: add ProjectID to Bedrock and Bedrock Mantle key configs for Mantle project scoping #5131
• dev

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

[greptile-apps]

Confidence Score: 5/5

This looks safe to merge.

• No blocking issues found in the changed code.

Important Files Changed

Filename	Overview
ui/app/workspace/providers/fragments/apiKeysFormFragment.tsx	Adds project ID inputs for Bedrock and Bedrock Mantle provider configuration.
ui/lib/schemas/providerForm.ts	Allows optional project ID values in the provider form schemas.
ui/lib/types/config.ts	Adds project ID fields to Bedrock config types and defaults.
ui/lib/types/schemas.ts	Allows optional SecretVar project IDs in frontend provider key schemas.

_{Reviews (4): Last reviewed commit: "feat: project id support for UI" | Re-trigger Greptile}

[Pratham-Mishra04]

Merge activity

• Jul 13, 2:14 PM UTC: A user started a stack merge that includes this pull request via Graphite.
• Jul 13, 2:18 PM UTC: Graphite rebased this pull request as part of a merge.
• Jul 13, 2:20 PM UTC: Graphite rebased this pull request as part of a merge.
• Jul 13, 2:21 PM UTC: Graphite rebased this pull request as part of a merge.
• Jul 13, 2:21 PM UTC: @Pratham-Mishra04 merged this pull request with Graphite.

The base branch was changed.