splunk-observability-cloud-integration-setup

You can automate the Splunk Observability Cloud integration setup by rendering a plan from a YAML spec and applying it idempotently. This handles UID and Service Account pairing, multi-org defaults, and Centralized RBAC provisioning automatically.

Yes, multi-org defaults and Centralized RBAC provisioning are supported together. The configuration enforces strict secret handling through file-based tokens and respects safety gates during the RBAC cutover process.

Yes, the integration setup supports both dry-run execution and preflight checks. Rendered plans are stored without secrets, allowing you to safely validate configurations before applying them to your cloud or enterprise deployments.

Token-based secret management enforces strict handling through file-based tokens. Rendered plans are stored with no secrets exposed, ensuring secure stateful idempotency across your Splunk Platform and Observability Cloud environments.

You can deploy on-demand resources like Log Observer Connect and the SIM Add-on by rendering them from a YAML spec. The setup orchestrates these configurations and can hand off installation tasks to other skills as needed.

Yes, pyyaml is required as a dependency to render the configuration plan. You provide a YAML spec which the setup script uses to apply integration sections idempotently across your Splunk deployments.