Add the ability to update CNAME and other DNS records

[mmckane]

Requiring a delete on a resource to update DNS is not efficient and makes using terraform to manage DNS useless. Please add the ability to update records with terraform, or provide any info as to why this is technically not possible.

[donwlewis]

@mmckane would you consider forcing a new resource on a change sufficient enough? We had a discussion on this in the previous maintainer project, and a quick fix was purposed with this pull request:

hashicorp/terraform-provider-infoblox#41

[mmckane]

@donwlewis I think that could be a good quick fix. could that be set for the other record types that couldn't be updated as well, as looking this might not be unique to CNAMEs?

I did dig enough and found thus issue/feature request in the underlying go client infobloxopen/infoblox-go-client#110

[PhilipWhiteside]

@donwlewis for my use that scenario would fit. I'm not precious about the original entries, just the result of name -> name. The entry is managed by Terraform, so nothing else should be tied to it outside of Terraform. However, performing a destroy, or taint, is challenging when we use a pipeline tied to git to push the changes into IB rather than local Terraform CLI.

I see that hashicorp/terraform-provider-infoblox#41 would support that. This is a MR into the old repo, is that going to be a problem as this repo has moved to here?

[PhilipWhiteside]

@deromemont You created this MR hashicorp/terraform-provider-infoblox#41 in an old repo which has been migrated here. The MR has not moved across with it. Are you able to push to this repo, or are you happy for me to copy your changes and do so on your behalf?

[deromemont]

@PhilipWhiteside you can copy my changes if you want ;)

[somashekhar]

We are working on this requirement.
We need to write update on infoblox go client and then implement the same at terraform.

[jfreeland]

What is the status of this?

[somashekhar]

@jfreeland work on this is almost complete and we are testing it along with other features. Can expect it under develop branch soon.

[somashekhar]

Now the feature is available at master branch. Will be available as part of v2.0.0