GitHub user svdimchenko created a discussion: Community terraform provider for Apache Superset
Hi Superset team and community 👋 I wanted to share something we've been building and open a conversation about its future. What we built We've created and published an open-source Terraform provider for Apache Superset: 👉 [gr8-toolkit/terraform-provider-superset](https://registry.terraform.io/providers/gr8-toolkit/superset/latest) It's built on top of the Terraform Plugin Framework (the modern SDK) and covers a solid portion of Superset's API surface. Here's what's implemented today: 12 resources: - superset_database — manage database connections - superset_meta_database — manage virtual (meta) databases - superset_dataset — manage datasets - superset_dataset_import — import datasets from a ZIP export - superset_chart_import — import charts from a ZIP export - superset_dashboard_import — import dashboards from a ZIP export - superset_dashboard_embedding — configure embedding settings for dashboards - superset_role — manage roles - superset_role_permissions — manage permission assignments for roles - superset_row_level_security — manage row-level security filters - superset_user — manage users - superset_css_template — manage CSS templates 7 data sources: - superset_role, superset_roles — look up roles by name or list all - superset_role_permissions — list permissions for a given role - superset_databases, superset_datasets — list all databases / datasets - superset_users — list all users - superset_css_template — look up a CSS template The provider is published on the Terraform Registry, has a full acceptance test suite (using httpmock so no real Superset instance is needed in CI), auto-generated docs, and a standard goreleaser-based release pipeline. The question We built this to scratch our own itch, but it's clearly useful beyond our team. Terraform/OpenTofu is a common IaC tool in the data engineering space, and having an officially-supported provider would lower the barrier for Superset adopters who want to manage their Superset configuration as code. Would the Superset project be interested in taking ownership or co-maintaining this provider under the apache/ GitHub org? We're happy to transfer the repository, contribute as maintainers under the project umbrella, or collaborate on whatever model makes sense for the community. Happy to answer any questions or jump on a call. Thanks for the great project! GitHub link: https://github.com/apache/superset/discussions/43513 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
