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	278b24cf67	Add sentry_dashboard_panel, resolving panels as their own resource ... The open design question named in the last three commits' README -- "a sentry_dashboard_panel resource (or a panels list block on this one)" -- is resolved: separate resource, matching api/dashboards.Handler's own shape (a panel is created/updated/deleted independently of its parent dashboard via its own endpoints, never by rewriting the dashboard's whole panel list). A nested list block would have forced every panel to be rewritten on any single panel's change, hiding fine-grained diffs a separate resource shows naturally -- the more idiomatic Terraform pattern for independently-lifecycled child resources, and the one that matches what the API actually does. Unlike sentry_alert_rule/sentry_notification_target, this resource supports a real in-place Update -- api/dashboards.Handler actually has a PUT /dashboards/{id}/panels/{panelId}. Only dashboard_id forces RequiresReplace: UpdatePanel's SQL matches WHERE id = $panelID AND dashboard_id = $dashboardID, so changing dashboard_id through the existing panel's URL wouldn't move it, it would just fail to match -- there's no API operation for "move a panel to a different dashboard." Panels have no standalone GET endpoint -- only GET /dashboards/{id}, which includes the full panels array. client.go's new getPanel fetches the parent dashboard and finds the panel by ID within it, returning the same *apiError{StatusCode: 404} shape a direct GET would whether the dashboard itself or just the panel within it is gone, so isNotFound works identically either way. This also means a bare panel ID isn't enough to import from -- ImportState takes "dashboard_id/panel_id" and splits on the last "/", the one resource here with a composite import identifier. query_language never accepts "sql" for panels specifically -- confirmed in api/dashboards's own validatePanel ("dashboards only support pipe-syntax queries, since the dashboard time-range picker is injected as leading query terms"), a real constraint from the API this client doesn't re-validate client-side (same "let the API be the one source of truth for validation" posture the other resources already take), but documented in the schema so it's not a surprise 400 from Create. sentry_dashboard_panel gets a matching data source too (dashboard_id + id both Required, unlike the other three data sources' single Required id, since getPanel itself needs both). Verified: client tests are real httptest.Server round trips, including getPanel finding the right panel within a real dashboard response and returning a recognizable not-found both when the panel is missing and when the parent dashboard itself is gone. Schema validation needs no Terraform binary. TestAccDashboardPanelResource_basic and TestAccDashboardPanelDataSource_basic are real acceptance tests, skip-gated by TF_ACC same as the other six -- the resource test proves a genuine in-place update (a title change, no plancheck needed since in-place update is the default expectation here, unlike the create/destroy-only resources). Not run against a live stack in this environment, same disclosed gap as everything else Docker-gated in this repo.	2026-08-15 10:40:27 -07:00