Do not install a HashiCorp registry provider named latticeddi/lattice — it is not published. Drive Lattice with curl or generate a provider from OpenAPI.
The product repo has a resource map (docs/terraform-provider-lattice.md and terraform/provider-sketch/) showing how a future provider would wrap:
lattice_prefix/lattice_subnet/lattice_poollattice_reservation/lattice_excludelattice_dns_server(secret refs, never plaintext after create)
Leases stay DHCP-owned. Force-release is POST /leases/{id}/release, not a Terraform resource.
If you automate today: Bearer token in CI, Idempotency-Key on creates, treat 409 overlap as the desired state already existing.