Remove Dynu provider version constraint

This commit is contained in:
beatz174-bit
2026-05-13 05:09:17 +10:00
parent fc5c882193
commit 5c38b92bc8
6 changed files with 57 additions and 30 deletions
+18 -20
View File
@@ -7,33 +7,27 @@ Dynu remains the authoritative DNS provider for existing records. Terraform here
## Provider
- Source: `beatz174-bit/dynu`
- Version constraint: `>= 0.1.0`
Authentication is local-only and must not be committed.
- Provider version is intentionally unpinned in this root to use the latest published release.
- Provider block uses `api_key` auth argument from the published provider schema.
## Credentials and auth
Use local `terraform.tfvars` (or environment variables if supported by the provider release you use).
Use local `terraform.tfvars` (or provider-supported environment variables).
Variables included:
- Required variable: `dynu_api_key`
- Optional placeholders for future provider auth changes: `dynu_username`, `dynu_password`
- `dynu_api_key` (sensitive)
- `dynu_username` (optional, sensitive)
- `dynu_password` (optional, sensitive)
Never commit:
> Keep real values out of git and out of shared logs.
## Safety
- Do not commit `terraform.tfvars`, `.tfstate*`, or `.terraform/`.
- Import/reconcile one domain or record at a time.
- Treat generated config as draft input, not final truth.
- `terraform.tfvars`
- `.terraform/`
- `*.tfstate*`
- credentials/secrets
## Safe validation commands
```bash
cd infrastructure/terraform/dynu
terraform fmt -check -recursive
terraform init -backend=false -input=false
terraform validate
@@ -48,11 +42,11 @@ terraform init
terraform plan
```
## Import workflow (placeholder examples)
## Import workflow (one object at a time)
```bash
terraform import dynu_dns_domain.lan_ddnsgeek_com '<provider-specific-domain-import-id>'
terraform state show dynu_dns_domain.lan_ddnsgeek_com
terraform import dynu_domain.lan_ddnsgeek_com '<provider-specific-domain-import-id>'
terraform state show dynu_domain.lan_ddnsgeek_com
terraform plan
```
@@ -64,4 +58,8 @@ $EDITOR imports.tf
terraform plan -generate-config-out=generated-dynu.tf
```
Confirm exact resource types and import ID formats from the provider docs before running imports.
Notes:
1. Confirm exact import ID formats from the provider docs.
2. For DNS records, add one `dynu_dns_record` resource at a time after confirming required arguments (`hostname`, `record_type`) from `terraform providers schema`.
3. Treat generated config as draft input; keep only stable, meaningful attributes in hand-maintained `.tf`.