Closed stephengroat closed 5 years ago
@markmpeterson saw that you cut the last release, any way you could help with this issue?
It looked like @alistanis was working on this already. Any chance a fix could get released sometime?
I'm having this same issue: Terraform will perform the following actions:
~ ns1_record.convos_etsy_com_MX regions.0.name: "mj" => "sg" regions.1.name: "sg" => "mj"
It will continually just flip flop the region names and TF cannot run without thinking changes have been made.
Can confirm this is still an issue with latest version of provider
The best way to deal with this currently is to to keep the regions ordered by name
in your .tf
files. This should keep terraform from flipping them around.
This was documented already, but I pushed a patch to emphasize this requirement a bit more in the docs.
Feel free to reopen or make a new ticket if this workaround is not acceptable, so we can understand the use case, etc.
Hi there,
Thank you for opening an issue. Please note that we try to keep the Terraform issue tracker reserved for bug reports and feature requests. For general usage questions, please see: https://www.terraform.io/community.html.
Terraform Version
Affected Resource(s)
Please list the resources as a list, for example:
ns1_record
Terraform Configuration Files
Expected Behavior
terraform plan
should be a repeatable function (as long the regions of the ns1_record in question are not changing in the background)Actual Behavior
terraform plan
forns1_record
withregions
does not appear to be a repeatable/reliable function,regions
in the list seems to switch positions all the timeSteps to Reproduce
terraform plan
terraform plan