[Bug]: AWs EKS addon cloudwatch observability - not destroyed after removed from plan. throws error when re-applyign plan

[alokkulkarni]

Welcome to the AWS Observability Accelerator

• [X] Yes, I've searched similar issues on GitHub and didn't find any.

AWS Observability Accelerator Release version

2.12.2

What is your environment, configuration and the example used?

Error: Provider produced inconsistent result after apply │ │ When applying changes to aws_iam_policy_attachment.aws_eks_cloudwatch_observability_attach, provider "provider["registry.terraform.io/hashicorp/aws"]" 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.

What did you do and What did you see instead?

i have commented the addon attachment and my cluster works fine.

Additional Information

Error: Provider produced inconsistent result after apply
│ 
│ When applying changes to aws_iam_policy_attachment.aws_eks_cloudwatch_observability_attach, provider "provider[\"registry.terraform.io/hashicorp/aws\"]" 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.