adds docker example for quickly testing out prod related issues --skip-pipeline

[akshaydeo]

Summary

Add Docker Compose example for Bifrost deployment with SQLite storage configuration.

Changes

• Created a Docker Compose configuration file for running Bifrost in a container
• Added a default SQLite-based configuration file for persistent storage
• Set up container health checks and restart policies
• Configured volume mounting for data persistence

Type of change

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

Affected areas

• Core (Go)
• Transports (HTTP)
• Providers/Integrations
• Plugins
• UI (Next.js)
• Docs

How to test

# Navigate to the examples/dockers directory
cd examples/dockers

# Start the Bifrost container
docker-compose up -d

# Verify the container is running
docker ps | grep bifrost

# Check the health endpoint
curl http://localhost:8080/metrics

Breaking changes

• No

Security considerations

• The configuration uses SQLite for both config and logs storage
• Default configuration allows all origins with "allowed_origins": ["*"]
• Direct API keys are disabled by default with "allow_direct_keys": false

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]

📝 Walkthrough

Summary by CodeRabbit

• New Features

  • Added comprehensive configuration framework supporting storage backends, client settings, governance policies, and pricing management.
  • Added Docker service deployment setup with health checks and persistent volume mounting.

• Bug Fixes

  • Fixed health check functionality by adding necessary runtime dependencies.

Walkthrough

The PR introduces Docker infrastructure for a bifrost service, adding a configuration file, docker-compose setup, and updating Dockerfiles to include wget for health check support.

Changes

Cohort / File(s)	Summary
Docker Infrastructure examples/dockers/data/config.json, examples/dockers/docker-compose.yml	New Docker Compose configuration for bifrost service v1.4.3 with SQLite-based configuration and logging stores, along with client settings for request handling, governance, and pricing.
Runtime Dependencies docs/plugins/building-dynamic-binary.mdx, transports/Dockerfile	Added wget to APK installation in Alpine-based runtime images to support health check operations via curl/wget commands.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

🐰 A docker-compose dance, so merry and bright,
With bifrost deployed and health checks in sight,
wget joins the party, no more shall we wait,
Alpine containers running first-rate! 🚀

🚥 Pre-merge checks | ✅ 2 | ❌ 2

❌ Failed checks (2 warnings)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 42.86% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.
Merge Conflict Detection	⚠️ Warning	❌ Merge conflicts detected (4 files): ⚔️ docs/plugins/building-dynamic-binary.mdx (content) ⚔️ framework/encrypt/encrypt.go (content) ⚔️ transports/Dockerfile (content) ⚔️ ui/app/_fallbacks/enterprise/lib/store/apis/index.ts (content) These conflicts must be resolved before merging into main.	Resolve conflicts locally and push changes to this branch.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title specifically references adding a Docker example for testing production-related issues, which aligns with the main changes of adding a Docker Compose configuration and SQLite config file.
Description check	✅ Passed	The description includes all required sections: Summary, Changes, Type of change, Affected areas, How to test, Breaking changes, Security considerations, and completed Checklist.

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

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch 01-31-adds_docker_example_for_quickly_testing_out_prod_related_issues

⚔️ Resolve merge conflicts (beta)

• Auto-commit resolved conflicts to branch 01-31-adds_docker_example_for_quickly_testing_out_prod_related_issues
• Create stacked PR with resolved conflicts
• Post resolved changes as copyable diffs in a comment

---

No actionable comments were generated in the recent review. 🎉

---

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

[akshaydeo]

• adds docker example for quickly testing out prod related issues --skip-pipeline #1496 👈 (View in Graphite)
• main

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

[github-actions]

🧪 Test Suite Available

This PR can be tested by a repository admin.

Run tests for PR #1496

[coderabbitai]

Actionable comments posted: 1

🤖 Fix all issues with AI agents

In `@examples/dockers/docker-compose.yml`:
- Around line 14-18: The healthcheck uses wget which is not present in the
alpine:3.22 base image, so update the service healthcheck or the image build:
either add installation of wget (or wget package name for Alpine) in the image
build step where the Dockerfile prepares the image (so the container built by
the Dockerfile has wget available), or change the healthcheck test in the
healthcheck configuration (the test array referencing "wget" in the healthcheck)
to use curl or another installed tool; ensure the chosen tool is actually
installed in the image (mirror the change in the corresponding Dockerfile build
steps that populate the runtime image).

🧹 Nitpick comments (1)

examples/dockers/docker-compose.yml (1)

3-3: Consider noting the pinned image version for future maintenance.

The image version v1.4.3 is pinned, which is good for reproducibility. For a testing example, you might want to add a comment in the documentation (e.g., README) mentioning that users should check for newer versions, or consider using a :latest tag if always testing against the newest release is preferred.

[coderabbitai]

Actionable comments posted: 2

🤖 Fix all issues with AI agents

In `@tests/scripts/migration-faker/main.go`:
- Around line 204-326: The code in generateEnhancedInserts currently skips
nullable JSON columns when ShouldBeNull(table.Name, col.Name) is true, which
omits the column instead of inserting an explicit NULL; change that behavior so
when col.IsNullable && ShouldBeNull(...) you set value = "NULL" (and do not
continue), so the column name and "NULL" are appended to columns/values; ensure
this happens before the later type-specific handling and that no additional
quoting/boolean conversion is applied to the NULL value.
- Around line 174-202: The build fails because several types and helper
functions referenced by GenerateAllInsertsEnhanced are missing; add concrete
definitions or stubs for the referenced symbols in the same package (or import
them): define types Table, Column, ForeignKeyInfo, ValueGenerator,
SchemaIntrospector with minimal fields/methods used by this file, and implement
functions LoadSchema, NewPostgresIntrospector, NewSQLiteIntrospector,
NewValueGenerator(dbType string, specialColumns map[string]map[string]string)
(returning a ValueGenerator), GetTableByName(tables []Table, name string)
*Table, GetForeignKeyMap(table *Table) map[string]ForeignKeyInfo, and
GetInsertOrder/any other helpers referenced by this package; ensure signatures
match how GenerateAllInsertsEnhanced and generateEnhancedInserts call them so
the package compiles (you can provide simple no-op or minimal implementations
that satisfy types and usage).

[akshaydeo]

Merge activity

• Feb 12, 8:12 PM UTC: A user started a stack merge that includes this pull request via Graphite.
• Feb 12, 8:12 PM UTC: @akshaydeo merged this pull request with Graphite.