[ISSUE] Provider v1.0.54 intersight_bulk_mo_merger broken again.

[scotttyso]

Bug Report Checklist

• Have you provided a full/minimal configuration to reproduce the issue?
• Have you [tested with the latest master] to confirm the issue still exists?
• Have you provided the terraform console logs with environment variable set to TF_LOG=trace?

Description

Terraform-provider-intersight version

v1.0.54

Configuration file

# module.profiles["map"].intersight_bulk_mo_merger.trigger_profile_update["Asgard/r143e-1-1-8"] will be created
resource "intersight_bulk_mo_merger" "trigger_profile_update" {
  class_id     = "bulk.MoMerger"
  merge_action = "Merge"
  object_type  = "bulk.MoMerger"
  sources {
    class_id    = "server.ProfileTemplate"
    moid        = "65d378aa77696e3201f89b24"
    object_type = "server.ProfileTemplate"
  }
  targets {
    class_id    = "server.Profile"
    moid        = "669557f477696e3201c4e0fc"
    object_type = "server.Profile"
  }
}

Actual output (Attach screenshots if applicable)

│ Error: Provider produced inconsistent result after apply
│
│ When applying changes to module.profiles["map"].intersight_bulk_mo_merger.trigger_profile_update["Asgard/r143e-1-1-8"], provider "provider[\"registry.terraform.io/ciscodevnet/intersight\"]" produced an unexpected new value: Root object was present,
│ but now absent.
│
│ This is a bug in the provider, which should be reported in the provider's own issue tracker.

Related issues/PRs

• [BUG] intersight_bulk_mo_merger broken in v1.0.48/v1.0.49/v1.0.50 for server_profile_templates #276

Suggest a fix

[scotttyso]

@vvb - This worked in v1.0.51 and v1.0.52. I didn't test with v1.0.53 so I am not sure if it worked in 1.0.53 for sure.

[jingiris05]

This issue should be resolved with the latest provider version. @scotttyso Could you please verify ?

[scotttyso]

This issue is resolved.