2 Commits

Include renames

Author	SHA1	Message	Date
jcoffey-dev	13cf9a30cb	Rebrand: Sentry -> Cairn OBS ... 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.	2026-08-21 20:53:32 -07:00
jcoffey-dev	30ae84cd04	Add sentry_notification_target, closing the alert-rule-as-code loop ... sentry_alert_rule.notification_target_id could previously only point at a target created outside Terraform (sentryctl/curl/the web UI) -- without this resource, "manage alert rules as code" was only half true. Same create/destroy-only shape as sentry_alert_rule and for the same reason: alerting has no PUT /targets/{id} either, confirmed down to notifystore.Store (Create/List/Get/Delete, no Update). client.go's notificationTarget type mirrors notifystore.Target's JSON shape. headers stays raw JSON bytes end to end -- the client has no opinion about its shape (neither does alerting's own Target type, json.RawMessage), and the resource layer round-trips it as a plain JSON-text string a caller provides via Terraform's jsonencode(). secret is marked Sensitive in the schema, but alerting's own GET /targets/{id} returns it unredacted (confirmed in notifystore/store.go -- no redaction at the store or handler layer, an existing property of alerting's API, not something this provider introduces). A new client test (TestGetNotificationTargetReturnsSecretUnredacted) documents that real behavior so a future change to it would be caught here, not discovered by surprise. Sensitive keeps the value out of plan/apply console output; it does not keep it out of Terraform state, the standard caveat for any sensitive attribute, named explicitly in the schema description and README rather than left implicit. Examples updated end to end: sentry_alert_rule's example now creates a real sentry_notification_target and references its .id, instead of a placeholder string. Verified: client tests are real httptest.Server round trips. Schema validation needs no Terraform binary. TestAccNotificationTargetResource_basic is a real acceptance test, skip-gated by TF_ACC same as the other two, including a plancheck.ExpectResourceAction assertion that a config change actually plans destroy-then-create, and (since secret really does round-trip unredacted) a real ImportStateVerify on the secret attribute rather than one papered over with ImportStateVerifyIgnore. Not run against a live stack in this environment, same disclosed gap as everything else Docker-gated in this repo.	2026-08-15 10:20:52 -07:00