Fix live-safe example default test IP for Dynu validation

This commit is contained in:
beatz174-bit
2026-04-23 15:42:00 +10:00
parent 029f108548
commit 016cdb3914
3 changed files with 4 additions and 4 deletions
+1 -1
View File
@@ -298,7 +298,7 @@ Live acceptance tests are opt-in and require:
Use `examples/live_safe_dns_record` when you want to safely validate writable provider behavior against a real Dynu account.
- This example creates a unique temporary subdomain in the form `<prefix>-<random>.<dynu_root_domain>`.
- It creates exactly one disposable `A` record using an obviously non-production test IP by default.
- It creates exactly one disposable `A` record using a default IPv4 value accepted by Dynu.
- It is designed so `terraform destroy` removes only the created disposable record from that run/state.
Safety guidance:
+1 -1
View File
@@ -10,7 +10,7 @@ then you remove it with `terraform destroy`.
- Hostname format is:
- `<test_prefix>-<test_suffix>.<dynu_root_domain>`
- Creates exactly one record:
- `A` record, default content `198.51.100.10`, default TTL `300`.
- `A` record, default content `1.1.1.1`, default TTL `300`.
- Does **not** import, update, replace, or delete existing production hostnames/records.
- `terraform destroy` removes only the disposable record in this state.
+2 -2
View File
@@ -23,9 +23,9 @@ variable "test_suffix" {
}
variable "test_ip" {
description = "Safe documentation/test IPv4 value for the disposable A record."
description = "IPv4 value for the disposable A record. Dynu rejects reserved documentation ranges (for example 198.51.100.0/24), so this default uses a public resolver address."
type = string
default = "198.51.100.10"
default = "1.1.1.1"
}
variable "test_ttl" {