You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Provider recognizes CNAME record exists already, and uses API to update it in-place using a PUT request on the api
Provider recognizes CNAME record exists already, and issues a Destroy and subsequent Create.
If intended behavior is to not overwrite records, by default, an additional input on the dme_dns_record signaling a forced overwrite is okay, would be useful to facilitate the above behavior.
Actual Behavior
Provider attempts to POST request to API (which is the CREATE) action on the API and is treated differently than an UPDATE (PUT HTTP verb), which is what causes the error.
Steps to Reproduce
Create conflicting CNAME record on a DOMAIN in your DNS Made Easy panel (test.example.com)
Modify config to reflect correct API key and secret, update dme_domain domain name
terraform apply
Important Factoids
This is a pared down, contrived, version of my terraform definition. Have confirmed this behavior with the, exact, above-pasted configuration (with my own domain name, obviously).
Also, I realize terraform doesn't touch things it doesn't know about. But, given the ethos that terraform isn't an all-or-nothing endeavor and we're trying to iteratively adopt it into our infrastructure, I need a way to either overwrite an existing CNAME record, or a feasible way to IMPORT a record into my tfstate.
References
N/A
The text was updated successfully, but these errors were encountered:
Terraform Version
Terraform v0.12.29
Affected Resource(s)
Terraform Configuration Files
Debug Output
Relevant part of the debug log pasted here:
https://gist.github.com/jimrubenstein/9e326175b1093c1bb38ced0f526ace79
Panic Output
N/A
Expected Behavior
I would expect one of two things to happen
If intended behavior is to not overwrite records, by default, an additional input on the
dme_dns_record
signaling a forced overwrite is okay, would be useful to facilitate the above behavior.Actual Behavior
Provider attempts to
POST
request to API (which is theCREATE
) action on the API and is treated differently than anUPDATE
(PUT
HTTP verb), which is what causes the error.Steps to Reproduce
test.example.com
)dme_domain
domain nameterraform apply
Important Factoids
This is a pared down, contrived, version of my terraform definition. Have confirmed this behavior with the, exact, above-pasted configuration (with my own domain name, obviously).
Also, I realize terraform doesn't touch things it doesn't know about. But, given the ethos that terraform isn't an all-or-nothing endeavor and we're trying to iteratively adopt it into our infrastructure, I need a way to either overwrite an existing CNAME record, or a feasible way to IMPORT a record into my tfstate.
References
N/A
The text was updated successfully, but these errors were encountered: