Importing a group member to `msgraph_resource` replaces the resource

[cwe1ss]

We're trying to import an existing group member into terraform using the following code

resource "msgraph_resource" "group_member" {
  url = "groups/${local.group_object_id}/members/$ref"
  body = {
    "@odata.id" = "https://graph.microsoft.com/v1.0/users/${local.member_id}"
  }
}

import {
  to = msgraph_resource.group_member
  id = "/groups/${local.group_object_id}/members/$ref/${local.member_id}"
}

however, when doing a terraform plan, this shows the following output:

  # msgraph_resource.group_member must be replaced
  # (imported from "/groups/27e22bce-..../members/$ref/ddd7099a-....")
  # Warning: this will destroy the imported resource
-/+ resource "msgraph_resource" "group_member" {
        api_version             = "v1.0"
      + body                    = {
          + "@odata.id" = "https://graph.microsoft.com/v1.0/users/ddd7099a-...."
        }
      ~ id                      = "ddd7099a-...." -> (known after apply)
        ignore_missing_property = true
      + output                  = (known after apply)
      ~ resource_url            = "groups/27e22bce-..../members/ddd7099a-...." -> (known after apply)
        url                     = "groups/27e22bce-..../members/$ref"
    }

We've taken the format for the import-id from the docs ("terraform import msgraph_resource.member /groups/group-id/members/$ref/00000000-0000-0000-0000-000000000000").

Is this a problem with the format of the "id" property in the import-block, or is importing group members maybe not yet supported in this provider?

[ms-henglu]

Hi @cwe1ss,

Thank you for taking time to open this issue.

The root cause is that the $ref resource doesn't support a way to get the latest state, after importing it, the body remains empty. That's why you're seeing the diff:

      + body                    = {
          + "@odata.id" = "https://graph.microsoft.com/v1.0/users/ddd7099a-...."
        }

And the body changes in the $ref resource replace the resource.

A workaround is that you can use lifecycle.ignore_changes to suppress the diff.

I'll work on improving it. Thanks!