"Terraform Internal ID" Extensible Attributes borne problem

[Mithun2507]

In the provider version 2.6 "Terraform Internal ID" Extensible Attribute was introduced. This also introduced a problem that if the attribute is lost on the infoblox side the terraform plan fails with the below error and blocks new deployments on the affected terraform workspace

Error: cannot find appropriate object on NIOS side for resource with ID 'record:a/ZG5zLmJpbmRfYSQuX2RlZmF***AxLDEwLjc2LjMyLjM:.abcs.com/abc': key Terraform Internal ID not found in map;

Recently, we encountered an incident where the attributes were lost on the Infoblox server, causing all Terraform plan jobs to fail. To resolve the issue, we had to import all the corresponding attributes, specifically the 'Terraform Internal ID,' back into the Infoblox server. Resources created prior to version 2.6 were not affected by the loss of the 'Terraform Internal ID' attribute on Infoblox.

For future releases, DNS records should be the primary attribute used to match the state file. The dependency on the internal_id attribute is causing this new problem.
Looking for possible solution in future releases

[JkhatriInfobox]

Hi @Mithun2507,

Thanks for reporting this issue. Could you please let us know how the "Terraform Internal ID" extensible attribute was deleted from the Infoblox server? This will help us reproduce and investigate the problem.

Please note that modifying/deleting this EA is not permitted as it is required for Terraform operations.
for more info refer the documentation: https://docs.infoblox.com/space/ipamdriverterraform/593692260/Management+of+Plug-In+Operations+with+Terraform+Internal+ID

Thanks!