Interest in an OpenTofu / Terraform Provider for Chaptarr?

[Josh-Archer]

Hi Chaptarr team!

I manage our media automation infrastructure declaratively via OpenTofu / Terraform (managing indexers, quality profiles, root folders, download clients, and settings as code).

While evaluating Chaptarr as a modern replacement for Readarr, I noticed that because Chaptarr refactors API schemas to support unified Audiobook + eBook handling, narrator entities, and new edition types, standard Readarr Terraform providers (devopsarr/readarr) are incompatible.

I maintain the Josh-Archer/terraform-provider-seerr provider (for managing Seerr / Jellyseerr / Overseerr instances via Terraform / OpenTofu).

I am considering developing a Terraform / OpenTofu Provider for Chaptarr (e.g. chaptarr_root_folder, chaptarr_quality_profile, chaptarr_naming, chaptarr_download_client, chaptarr_indexer, etc.).

A few quick questions for the maintainers and community:

1. API Stability: Are the /api/v1 or /api/v3 REST API endpoints in a stable enough state for a provider to target, or are major breaking schema refactors still planned during the current beta?
2. Community Interest: Is there interest from the Chaptarr community in having a Go-based OpenTofu/Terraform provider for infrastructure-as-code deployments?
3. OpenAPI / Swagger Spec: Does Chaptarr generate or export an OpenAPI/Swagger JSON specification (/api/v1/openapi.json or similar) that could assist in provider code generation?

Thanks for building an awesome project!