DevOps & Infrastructure
Terraform Provider Offering
Decides whether a SaaS or API platform should ship its own Terraform/OpenTofu provider, then builds and maintains it - API readiness gate, adopting a community provider, resources vs data sources, secrets, import and drift, state upgrades, sandbox acceptance tests, signed releases on the Terraform and OpenTofu registries, versioning and deprecation. Use whenever a vendor mentions building or maintaining a Terraform provider, OpenTofu provider, terraform-plugin-framework, publishing a provider, perpetual diffs in a provider they maintain, or customers wanting to manage the product as infrastructure as code. Not for using or upgrading a third-party provider, nor for modules. Do NOT use for SDK package registries - use samber/developer-platform-skills@sdk-package-publishing.
- Publisher / source
- samber/developer-platform-skills (found on skills.sh)
- Upstream record
- samber/developer-platform-skills
- Version
- Version 3
- Published
- Publication review
- Approved for publication
- Content fingerprint
6512688dec443e3978e625a74cca35ce4891a0d4b69ca951e056d92ce22a7fba