0.6.6-beta breaks custom_attributes in the "endpoint" resource

[rfc1149]

Upon upgrading my provider version to v0.6.6-beta or later, I'm receiving an error that looks like this:

   resource "ciscoise_endpoint" "test_laptop" {
parameters.0.custom_attributes.0.custom_attributes: '' expected type
'string', got unconvertible type
'isegosdk.ResponseEndpointGetEndpointByNameERSEndPointCustomAttributesCustomAttributes',
value: 'map[Owner:]'

my terraform code works just fine on v0.6.5-beta or earlier, it's a very straightforward resource definition:

resource "ciscoise_endpoint" "test_laptop" {

  parameters {
    description             = "Set with TF"
    group_id                = "<group_id>"
    mac                     = "<mac>"
    name                    = "test_laptop"
    static_group_assignment = "true"
  }
}

I believe that the root cause here is that 0.6.6-beta changed this line to be a TypeString instead of a map:

terraform-provider-ciscoise/ciscoise/resource_endpoint.go

Line 209 in adf2efe

Type: schema.TypeString, //TEST,

Indeed, if we look at the data source for this same thing, we see that it's listed as a TypeMap:

terraform-provider-ciscoise/ciscoise/data_source_endpoint.go

Line 142 in 48388aa

Type: schema.TypeMap,

We can see that it was changed in the 0.6.6-beta commit based on the git blame, and it shows here:
48388aa#diff-6b7a14e67c9c08afade28f67ddd6a9c6efe8dac58b19e70ba61e2f326010129f

Could we get this reverted back to a map?

[fmunozmiranda]

Hi @rfc1149 could you please retry it with last version of ISE provider and update us if bug still there?

[fmunozmiranda]

If we don´t get answer, this issue will be closed in next 24 hours.

[rfc1149]

Hi sorry I am on holiday and hadn't been checking this issue super closely since it has been so long since I opened it. I will give it a try next week!

[fmunozmiranda]

Thank you for your answer, we will wait your tests.

[rfc1149]

I'm still seeing the same issue on v0.8.1-beta

[fmunozmiranda]

@rfc1149 could you please pass us debug of provider?

[rfc1149]

Unfortunately that's a bit tricky in my environment, is the information in the original post insufficient for a reproduction of the issue?