Updating a resource with id in the payload about terraform-provider-restapi HOT 4 OPEN

I'm running into a similar situation, with the API I am interacting with, I can POST /people to create a user object, and I can refresh the data with GET /people/{id} But the interface does updates with a POST /people the same as create, but when an ID is included in the data payload, it's considered an update.
I'd love to be able to do something like the following with {id} being rewritten to the actual ID value on the update call.

resource "restapi_object" "users" {
  path = "/people"
  
  data = jsonencode({
    firstName          = "John"
    lastName           = "Doe"
  })
  update_data = jsonencode({
    id                        = "{id}"
    firstName          = "John"
    lastName           = "Doe"
  })
}

from terraform-provider-restapi.

Actually just discovered that copy_keys provides functionality for exactly this purpose!

so the fix would be:

provider "restapi" {
  uri                  = "https://dremio.xxx.com/api/v3"
  debug                = true
  write_returns_object = true
  create_method        = "POST"
  update_method        = "PUT"
  copy_keys            = ["id"]

  headers = {
    "Content-Type"  = "application/json"
    "Authorization" = "Bearer ..."
  }
}

from terraform-provider-restapi.

@ivank I am having the same request but I am really struggling with this option do you perhaps have piece of example code to see how this would work?

from terraform-provider-restapi.

Thanks @ivank, your post saved my life with this use case. Works perfectly for another use case as well with AzureDevops release/definitions's REST API.
I personnaly used the following configuration in the restapi provider

copy_keys = ["id", "revision"]

from terraform-provider-restapi.