resource "dme_dns_record" "dyn_record" {
domain_id = "domain ID"
name = "foo-dyndns"
type = "A"
value = "1.2.3.4"
ttl = 600
dynamic_dns = true
password = "aPassword"
Debug Output
NA
Panic Output
NA
Expected Behavior
value is currently a required parameter. I would expect it to be optional in case of dynamic_dns=true to avoid overriding the dynamic IP on the next terraform apply.
I would expect the following input to be accepted by making value optional:
resource "dme_dns_record" "dyn_record" {
domain_id = "domain ID"
name = "foo-dyndns"
type = "A"
ttl = 600
dynamic_dns = true
password = "aPassword"
Alternative would be to ignore the value when the record already exists.
Actual Behavior
On each terraform apply the IP address uploaded by my router is overriden by hardcoded value in terraform. With this we loose the dynamic capabilities.
Steps to Reproduce
terraform apply
modify the IP address either by the UI or with a dyndns client
Terraform Version
Affected Resource(s)
Terraform Configuration Files
Debug Output
NA
Panic Output
NA
Expected Behavior
value is currently a required parameter. I would expect it to be optional in case of dynamic_dns=true to avoid overriding the dynamic IP on the next terraform apply.
I would expect the following input to be accepted by making value optional:
Alternative would be to ignore the value when the record already exists.
Actual Behavior
On each terraform apply the IP address uploaded by my router is overriden by hardcoded value in terraform. With this we loose the dynamic capabilities.
Steps to Reproduce
terraform apply
terraform apply
-> IP change from step 2 is lost.Important Factoids
NA
References
NA