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.
22 lines
955 B
Docker
22 lines
955 B
Docker
# Build context must be the repo root (sentry/), not agent/, since this
|
|
# needs both agent/ and proto/:
|
|
# docker build -f agent/Dockerfile -t cairnobs-agent .
|
|
|
|
FROM rust:1-alpine AS builder
|
|
RUN apk add --no-cache musl-dev protobuf-dev protobuf
|
|
WORKDIR /src
|
|
COPY proto ./proto
|
|
COPY agent ./agent
|
|
WORKDIR /src/agent
|
|
# file-tail is additive (no extra deps -- see Cargo.toml's [features]
|
|
# doc comment) and needed on any host whose logs aren't in journald
|
|
# (e.g. nginx's plain access/error log files), so it's built in
|
|
# alongside the journald default rather than left as an opt-in most
|
|
# deployments would otherwise have to remember to ask for.
|
|
RUN rustup target add x86_64-unknown-linux-musl \
|
|
&& cargo build --release --target x86_64-unknown-linux-musl -p cairnobs-agent --features journald,file-tail
|
|
|
|
FROM scratch
|
|
COPY --from=builder /src/agent/target/x86_64-unknown-linux-musl/release/cairnobs-agent /cairnobs-agent
|
|
ENTRYPOINT ["/cairnobs-agent"]
|