We manage Kviklet alongside a platform that is otherwise provisioned with Terraform, and we would like to manage Kviklet objects (connections, roles, role-sync mappings, policies, users/API keys, configuration) declaratively as well. Today this is only possible via the UI or by scripting the REST API, which we currently do with an unwieldy shell script. A first-party Terraform provider would let us express Kviklet config as code and reconcile it through our normal pipelines.

Use case

• GitOps for Kviklet: configuration tracked in the same repos and review process as the rest of our platform, with terraform plan surfacing drift.
• Reproducible environments: stand up dev/staging/prod Kviklet instances with identical roles, mappings and policies from one module, replacing imperative bootstrap scripts.

Notes

• A stable, documented OpenAPI spec would be a step in this direction, and make the creation of a community provider feasible.
• We are happy to share our current sync script, helm chart, and the resource shapes we have found useful as input.
• The Kviklet website already displays a Terraform logo, so I assume this might be on the roadmap already.

Environment

Kviklet 0.7.0, Helm on Kubernetes.