Add godaddy-tofu provider to terraform and configure DNS records #435
Labels
No labels
domain:backend
domain:devops
domain:frontend
status:approved
status:in-progress
status:needs-fix
status:qa
type:bug
type:devops
type:feature
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
ldraney/pal-e-platform#435
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Type
Feature
Lineage
Related to
ldraney/godaddy-tofu #11(DNS resource — completed).Repo
ldraney/pal-e-platformUser Story
As a platform operator
I want DNS records managed as IaC in pal-e-platform
So that domain configuration is version-controlled and reproducible
Context
The godaddy-tofu provider is complete (all issues closed, CI active). DNS A records for
palinks.appandlandscaping-assistant.appcurrently point to the Hetzner edge VPS at178.156.129.142but are managed manually through the GoDaddy console. This ticket brings those records under Tofu management.The provider is not in any public registry. Use
dev_overridesin~/.terraformrcpointing to thego installoutput of godaddy-tofu, or copy the binary to the local plugin cache directory.File Targets
Files the agent should modify or create:
terraform/versions.tf-- add godaddy provider torequired_providersblockterraform/providers.tf-- addprovider "godaddy"config block with api_key/api_secret from SOPS secretsterraform/dns.tf(new) --godaddy_dns_recordresources for palinks.app and landscaping-assistant.app A records pointing to 178.156.129.142terraform/variables.tf-- add variables for GoDaddy API credentialsFiles the agent should NOT touch:
terraform/main.tf-- unrelated infrastructureterraform/k3s.tf-- cluster config, not DNSFeature Flag
none
Acceptance Criteria
tofu plan, then 2 DNS record resources are shown (palinks.app A, landscaping-assistant.app A)tofu apply, then records are created in GoDaddy DNSdig palinks.appanddig landscaping-assistant.app, then both resolve to 178.156.129.142Test Expectations
tofu plansucceeds without errors and shows expected resourcestofu applycreates records,tofu destroyremoves themdigqueries confirm correct resolution after applycd terraform && tofu planConstraints
dev_overridesin~/.terraformrcor copy to plugin cacheldraney/godaddy-tofu #11(DNS resource CRUD) is satisfied — provider is complete and tested178.156.129.142(Hetzner edge VPS running Caddy + Tailscale reverse proxy)Checklist
Related
pal-e-platform-- project this affectsldraney/godaddy-tofu-- custom provider repoldraney referenced this issue2026-06-14 20:19:52 +00:00
Scope Review: NEEDS_REFINEMENT
Review note:
review-1462-2026-06-14File targets are incomplete and one is misleading --
required_providerslives inversions.tf, notproviders.tf. Secrets path is too vague for an agent to act on. Arch traceability gap:arch:pal-e-platformlabel has no backing note.[BODY]Addterraform/versions.tf,terraform/variables.tf, andterraform/secrets.auto.tfvars.exampleto File Targets[BODY]Clarify provider binary installation method (dev_overrides or go install)[BODY]Update Constraints -- godaddy-tofu #11 is now closed[LABEL]Changearch:pal-e-platformtoarch:godaddy-tofu(note exists), or[SCOPE]createarch-pal-e-platformnoteScope Review: APPROVED
Review note:
review-1462-2026-06-14-r2Re-review after refinement -- all 4 findings from initial review addressed. Template complete, file targets verified against live repo, dependencies satisfied, acceptance criteria testable. Ready for implementation.
Non-blocking acknowledged gap: no
arch-pal-e-platformnote exists (platform-wide gap, tracked separately).