Role read when managing_org is gone about terraform-provider-hsdp HOT 6 CLOSED

@loafoe nevermind, it was a mistake on my end, I thought the IAM org was removed, but it is actually still there, what happened is that when they offboarded the org from the edi-platform, the automation removed the permissions our service identity had there.

Closing the issue for now, sorry for the confusion and thanks for your support 😄

from terraform-provider-hsdp.

@jdelucaa yes, this can be added here as well as a workaround. That's much simpler than trying to change the arguably invalid response from the IAM API

from terraform-provider-hsdp.

@jdelucaa which version of the provider are you using? The IAM team actually released a fix for INC0080073 recently so the latest provider version should actually return 404. The setup you are describing might trigger another corner case so having as much detail as possible will help here.

from terraform-provider-hsdp.

@jdelucaa also, if we would return 404 then Terraform would mark the resource as gone and will try to recreate it as part of the run no? What about the managing ORG of this role?

from terraform-provider-hsdp.

oh, my bad, I haven't tested the latest version of the provider yet. let me try it and get back with more details.

from terraform-provider-hsdp.

@jdelucaa also, if we would return 404 then Terraform would mark the resource as gone and will try to recreate it as part of the run no? What about the managing ORG of this role?

Yes, you are right, in the latest version of the provider it returns a 404 and it marks the resource as gone, I was using an older version. 👍

from terraform-provider-hsdp.