Description
Three provider kinds activate Grafana Cloud observability products per stack: AppO11yConfigV1alpha1, DBO11yConfigV1alpha1 and K8sO11yConfigV1alpha1, all in the cloud family. Each is a singleton with a fixed metadata uid of global and a spec carrying an enabled boolean. They need no bootstrap and no credential beyond the per-stack ProviderConfig this repository already vends.
Add a products object to the stack request spec with three booleans, defaulting off, rendering one singleton per enabled product.
State plainly in the README that these are activation toggles, not configuration. The configurable surface for Kubernetes Monitoring lives in Helm chart values and for Application and Database Observability in onboarding flows, none of which is reachable from this provider. An API field that implies otherwise is worse than an absent one.
Verified present in the pinned provider, so this needs no pin bump.
Acceptance Criteria
- #1 spec.products carries applicationObservability, kubernetesObservability and databaseObservability booleans, each defaulting false
- #2 Each enabled product renders its singleton with the fixed global external name and no others
- #3 Disabling a product after enabling it is handled explicitly and the behaviour is documented
- #4 The README states these are activation toggles and names where the real configuration lives
- #5 A catalog example enables at least one product and renders
Definition of Done
- #1 ./scripts/validate.sh passes locally
- #2 hosted Validate workflow passes on the completing commit
Implementation Plan
Wave 2: validate the product singleton rendering completed in the root prerequisite, add an inert catalog example, and document toggle semantics; root wires and gates.
Implementation Notes
Wave 1 lane G disposition, 2026-09-08: Not started and Parked because the mandatory root pre-fan-out pass did not produce a pushed seam SHA after route metadata was unavailable. Resume after GCV-0032 completes the section 5.0 pass, then spawn EXECUTION on gpt-5.6-luna at max effort with fork_turns none and the pushed pre-pass SHA. No acceptance criterion or Definition of Done item was checked.
Wave 2 verification: focused product race tests proved exact singleton rendering and withdrawal behavior; catalog, integrated local gate, and hosted Validate run 34233686654 passed.
Final Summary
Delivered opt-in Application, Kubernetes, and Database Observability activation toggles with fixed global singleton identity and documented configuration boundaries. Completing SHA 83f81afee7526fd6e7c4ec0a47675774d00036b8; hosted Validate run 34233686654 succeeded.