Inconsistent results due to compartment_id for bloxone_ipam_address_block and bloxone_ipam_subnet resources

[paulspiegel]

I'm encountering an error when creating new subnets and address blocks. This error also occurs whenever I rerun the plan/apply.

I'm running this terraform code using a Service API key that is granted access to an Access View which is tied to a parent address block 10.0.0.0/8. The subnets and address blocks I'm creating are all under this address block. The resources are being successfully created in UDDI (and that access view is being inherited) but the Terraform applies are erroring each time because of an inconsistent value for the compartment_id

My code:

resource "bloxone_ipam_subnet" "subnet" {
  address = var.address
  cidr    = var.cidr
  name    = var.name
  comment = var.comment
  space = "ipam/ip_space/<removed>"
}

resource "bloxone_ipam_address_block" "block" {
  for_each = toset(var.spoke_allocated_ip_ranges)
  address  = split("/", each.value)[0]
  cidr     = split("/", each.value)[1]
  name     = var.spoke_name
  space = "ipam/ip_space/<removed>"
}

Error from applying bloxone_ipam_subnet

Error: Provider produced inconsistent result after apply
When applying changes to module.spoke.module.spoke-subnetwork.module.build-uddi-networks["us-central1/gcp-nonprod-euc-general-us-central1-01"].bloxone_ipam_subnet.subnet, provider "provider[\"registry.terraform.io/infobloxopen/bloxone\"]" produced an unexpected new value: .compartment_id: was cty.StringVal(""), but now cty.StringVal("96a23.").

This is a bug in the provider, which should be reported in the provider's own issue tracker.

Error from applying bloxone_ipam_address_block

When applying changes to module.spoke.bloxone_ipam_address_block.block["10.66.144.0/20"], provider "provider[\"registry.terraform.io/infobloxopen/bloxone\"]" produced an unexpected new value: .compartment_id: was cty.StringVal(""), but now cty.StringVal("96a23.").

This is a bug in the provider, which should be reported in the provider's own issue tracker.

[unasra]

Hi @paulspiegel

Thank you for raising this issue !

As per our preliminary observation, it seems like backend behaviour has been shifted to treat the parent's compartment as the child's compartment by default . While on the other hand , we are setting default value for the children ( Address Block and Subnet in this context ) as the unassigned or "" compartment , which seems to be causing the issue. I think removing the default value from the compartment attribute should fix this.

Should be fixed by #242. But will run a few more tests to confirm this.