Deployment: godaddy-tofu
Deployment: godaddy-tofu
Diagram
Components
| Component | Purpose | Notes |
|---|---|---|
| Developer workstation | Local development and testing | <code>go install</code> places binary in local plugin cache |
| Woodpecker pipeline | CI — runs tests, builds releases | Needs GODADDY_API_KEY/SECRET for acceptance tests |
| Forgejo release | Binary distribution | goreleaser produces multi-arch binaries |
| pal-e-platform | Consumer — IaC repo that uses the provider | References provider in <code>required_providers</code> block |
| api.godaddy.com | GoDaddy API | Production endpoint for DNS/domain management |
Key Decisions
- Local plugin cache for development (
~/.terraform.d/plugins/) — no registry needed during development - goreleaser for releases — standard Terraform provider distribution pattern
- Woodpecker CI needs real API credentials for acceptance tests — no mocking the API
- pal-e-platform is the first and primary consumer — provider design driven by platform needs
Related
arch-domain-godaddy-tofu— entity definitionsarch-dataflow-godaddy-tofu— runtime API flowproject-godaddy-tofu— project page