Full rebrand across cosmetic branding, code identifiers, and infrastructure/data-plane naming, using the supplied Cairn OBS logo package. Cosmetic: favicon/logo swap (also closes a stale license-audit finding -- the old favicon was SvelteKit's unreplaced scaffold logo), new centered welcome landing page, larger/legible sidebar logo, page titles, CLAUDE.md/README/docs prose. Code identifiers: Go module path github.com/sentry/sentry -> github.com/cairnobs/cairnobs across all 13 modules and ~91 files (protoc regenerated); Rust crates sentry-agent/sentry-parser/sentry-search -> cairnobs-*; CLI sentryctl -> cairnobsctl; Terraform provider fully renamed (sentry_dashboard etc. -> cairnobs_dashboard, provider type, env vars); every session/auth cookie name; agent config paths and Windows service identity. Deliberately preserved: the gRPC wire protocol's protobuf packages (sentry.logs.v1, sentry.agent.v1) and their Go import directory (proto/sentry/...) -- renaming the wire-level package would break every currently-deployed agent binary (confirmed two real hosts, including mail.inbuxa.com, are actively streaming through this exact contract) until rebuilt and redeployed in lockstep with an ingest cutover. Only the Go module path wrapping the generated code changes. Infrastructure: every docker-compose container name (root and three component-level compose files); the Helm chart (directory, Chart.yaml, named-template helpers, all templates, values.yaml image repos); Kubernetes Operator (CRD group sentry.io -> cairnobs.io, both CRD YAML files, Go identifiers, RBAC markers); the coupled enterprise/tenantcrd package. Caught and fixed real path-coupling bugs along the way: the Helm chart's search/ingest volume mounts and the dev-only-credential detection constant vs. docker-compose.yml's literal values had to move together or a security warning would have silently stopped firing. Data plane: Postgres database sentry_metadata -> cairnobs_metadata and role sentry -> cairnobs; ClickHouse database sentry -> cairnobs; Kafka topic sentry.logs.raw -> cairnobs.logs.raw and its consumer groups. Source-level defaults, docker-compose.yml, and every migrate.sh/ provision script default updated together; already-applied migration files left untouched per this repo's immutable-migration convention. Verified at every layer: all 13 Go modules build/vet/test clean, both Rust workspaces (agent, search) build/clippy/test clean, npm run check/ build clean, docker compose config validates on all four compose files. Live-verified against a real docker stack multiple times through this work, including a final fresh-volume run confirming the actual renamed Postgres database/role, ClickHouse database, and Kafka topic all work end to end with a real login and query, zero console errors.
63 lines
2.4 KiB
Go
63 lines
2.4 KiB
Go
// Package router is the per-operation provider/model dispatch layer
|
|
// /docs/phase-7-ai-design.md's "per-operation provider/model
|
|
// configuration" section decided to build now rather than defer --
|
|
// Complete's tight latency budget and Translate/Fix's quality needs are
|
|
// already in tension under a single-model-for-everything design, not a
|
|
// hypothetical future conflict.
|
|
//
|
|
// Deliberately thin: a lookup table from Operation to whichever
|
|
// provider.Provider was configured for it, falling back to one default
|
|
// when an operation has no specific override. This package makes no
|
|
// decisions about *which* provider is good for an operation -- that's
|
|
// deployment configuration, resolved once at startup by whoever
|
|
// constructs a Router (main.go, once the AI HTTP handlers exist to
|
|
// consume it).
|
|
package router
|
|
|
|
import "github.com/cairnobs/cairnobs/api/ai/provider"
|
|
|
|
type Operation string
|
|
|
|
const (
|
|
OpTranslate Operation = "translate"
|
|
OpComplete Operation = "complete"
|
|
OpExplain Operation = "explain"
|
|
OpFix Operation = "fix"
|
|
)
|
|
|
|
// Router selects a provider.Provider per Operation. Not itself a
|
|
// provider.Provider -- callers ask For(op) and then call the operation
|
|
// they actually need on the result, rather than this type trying to
|
|
// implement all four methods and dispatch internally, which would just
|
|
// be an extra layer of indirection for no benefit.
|
|
type Router struct {
|
|
byOp map[Operation]provider.Provider
|
|
fallback provider.Provider
|
|
}
|
|
|
|
// New builds a Router. fallback must not be nil -- every operation
|
|
// resolves to *some* provider, even a deployment that never calls
|
|
// SetOperation and just wants one model for everything.
|
|
func New(fallback provider.Provider) *Router {
|
|
return &Router{byOp: make(map[Operation]provider.Provider), fallback: fallback}
|
|
}
|
|
|
|
// SetOperation overrides which provider handles op. Call once per
|
|
// operation that needs a non-default model at startup configuration
|
|
// time -- not intended to change at runtime (a Router isn't
|
|
// synchronized for concurrent SetOperation/For calls, matching every
|
|
// other "assembled once in main.go, read-only after that" config shape
|
|
// in this codebase, e.g. Handler's fields in queryapi).
|
|
func (r *Router) SetOperation(op Operation, p provider.Provider) {
|
|
r.byOp[op] = p
|
|
}
|
|
|
|
// For returns the provider configured for op, or the fallback if none
|
|
// was set specifically.
|
|
func (r *Router) For(op Operation) provider.Provider {
|
|
if p, ok := r.byOp[op]; ok {
|
|
return p
|
|
}
|
|
return r.fallback
|
|
}
|