Terraform provider via Speakeasy (same OpenAPI spec pipeline)
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- openapi, python, terraform
- Domain
- infrastructure
Research direction
Start with .speakeasy/gen.yaml and the linked Speakeasy Terraform documentation to determine how a Terraform provider target would fit the existing OpenAPI generation pipeline. Done would mean the provider can be generated from the same spec, but the issue does not identify implementation files, tests, or a concrete resource scope.
Written by the indexing model from the issue text.
Description
Summary
Clerk already uses Speakeasy to generate this Python SDK from an OpenAPI spec. Speakeasy also supports generating a Terraform provider as an output target from the same spec — meaning much of the scaffolding for a Clerk Terraform provider is already in place.
This would let teams manage Clerk configuration (applications, organizations, roles, permissions, etc.) as infrastructure-as-code alongside the rest of their stack.
Context
- Clerk roadmap item (221 upvotes, currently in backlog): https://feedback.clerk.com/roadmap?id=82b49526-b724-4811-b999-bee569b94143
- Speakeasy Terraform support: https://www.speakeasy.com/docs/terraform
Since clerk-sdk-python is already generated via Speakeasy from an OpenAPI spec (see .speakeasy/gen.yaml), adding a Terraform provider target to the same pipeline would be a relatively low-lift way to deliver on the roadmap item — no need to hand-author provider resources or maintain a separate API client.
What we'd use it for
We're building an IaC engine for Clerk (roles, permissions, organization settings) and currently drive it through the Python SDK. A Terraform/Pulumi provider would let us (and others) manage Clerk declaratively with proper state tracking, drift detection, and plan/apply workflows — the same way we manage GCP, Datadog, and other services.
Ask
Would the Clerk team consider adding a Terraform provider output to the existing Speakeasy generation pipeline? Happy to help test or contribute if there's interest.
- Dominant language
- Python
- Stars
- 186
- Forks
- 47
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from clerk/clerk-sdk-python
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
clerk/clerk-sdk-python#243 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
clerk/clerk-sdk-python#241 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
clerk/clerk-sdk-python#227 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 62/100
clerk/clerk-sdk-python#231 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 38/100
clerk/clerk-sdk-python#230 ·
All issues in clerk/clerk-sdk-python
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 83/100
PedestrianDynamics/pyFDS-Evac#766 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 1-3 hours Newbie friendliness 91/100
alchaincyf/nuwa-skill#86 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 2 days
-
Docs Needs Triage
Difficulty 1/5 Under an hour Newbie friendliness 88/100
pandas-dev/pandas#71055 ·
Maintainers usually reply within 1 day
-
[Bug]: graphify reads files that git's global ignore file hidesPossibly taken @smngvlkz claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Graphify-Labs/graphify#4335 · 1 comment ·
Maintainers usually reply within 1 day