Support reverting remote changes

[michaelPotter]

Hi, @DRuggeri. This PR is to fix issue #81 - provider doesn't refresh state against the remote state.

I've updated the restapi_object resource to now attempt to revert any changes made outside of Terraform.

To support the cases where the API adds metadata out of our control, like "last_modified", you can add those paths to ignore_changes_to. For deeply nested paths, you can go "metadata.last_modified".

To get the old behavior back, set ignore_all_server_changes to true.

For example, a declaration might look like this:

resource "restapi_object" "Linguini" {
  path      = "/api/cats"
  object_id = "Linguini"

  data = jsonencode({
    name    = "Linguini"
    color   = "tabby"
    hobbies = {
      hunting = "birds"
      eating  = "plants"
    }
  })

  ignore_changes_to = [
    "name",
    "last_modified",
    "hobbies.sleeping",
  ]
}

Where the response returned by the server:

• removes the name field
• adds the last_modified field
• add the hobbies.sleeping field

Let me know what you think and if you'd like any changes. I don't have a ton of experience in Go, so if anything looks wrong just let me know.

[fancybear-dev]

Nice! Will test it out in our production environment likely this week and let you know if we find any bugs/improvements.

If you want to track; hnhdev#5

We've forked, because this upstream repository is currently in hibernation as far as we can tell - or at least way to slow for our workflow.

[amvapor]

Is anything holding this Pull Request back?

[DRuggeri]

Thanks, @michaelPotter - I love this idea and it is something I've wanted to add to the provider for some time! Detecting deltas has been a tricky topic, so I will aim to dig into the implementation soon to have a look and offer better feedback. This is exciting!!!

Also, thanks for the patience! As mentioned in the readme, we keep the provider up to date but features are ssssllllloooooowwwwww.