Hi Jingsong, +1 from me.
I support creating apache/terraform-provider-paimon as a separate repository. The provider has its own Go dependencies and release cycle, and the REST Catalog API provides a clean integration boundary. The proposed initial scope of databases and tables looks reasonable. Stable resource IDs, import, state refresh, and idempotent operations should be covered first. The repository name also looks good. The PMC can help confirm the bootstrap and initial maintainer process. Best, Jerry On Thu, Aug 20, 2026 at 11:56 AM Jingsong Li <[email protected]> wrote: > Hi community, > > I would like to propose creating a new repository named > apache/terraform-provider-paimon, similar to Apache Iceberg's > Terraform provider: > > https://github.com/apache/terraform-provider-iceberg > > The goal is to let users manage Apache Paimon catalog metadata through > Terraform and OpenTofu, using Paimon's REST Catalog API as the > control-plane interface. > > I have been working on an initial Go prototype based on the Terraform > Plugin Framework. The current prototype includes: > > - paimon_database resource and data source > - paimon_table resource and data source > - REST Catalog /v1/config discovery and catalog-prefix handling > - Bearer token authentication > - Alibaba Cloud DLF AK/STS request signing > - refreshable STS credentials from a local token file or ECS RAM role > - unit, race, vet, and build verification > > A separate repository would make the provider easier to discover, > release, and maintain independently, while keeping the Paimon Java > repository focused on the core system. It would also follow the > precedent established by terraform-provider-iceberg. > > For the initial scope, I suggest focusing on database and table > lifecycle management through the REST Catalog API. More advanced > objects and schema evolution could be added incrementally after the > basic provider contracts are stable. > > I would appreciate feedback on the following points: > > 1. Does the community support creating this repository? > 2. Is apache/terraform-provider-paimon the preferred repository and > provider name? > 3. What process should we follow to contribute the current prototype > and establish initial maintainers? > 4. Are there additional capabilities or compatibility requirements > that should be included in the first milestone? > > If there is general agreement, I can prepare the initial code > contribution and a more detailed repository bootstrap checklist for > review. > > Best, > Jingsong >
