Root resource was present, but now absent error

[askaribragimov]

I make use of the module to create an AWS Lambda. I am changing the block as shown below:

//WAS

  attach_policy = true
  policy        = aws_iam_policy.allow_ssm_read.arn
  
//NOW

attach_policies = true
  policies = [
    aws_iam_policy.allow_ssm_read.arn,
    "arn:aws:iam::aws:policy/CloudWatchLambdaInsightsExecutionRolePolicy"
  ]
  number_of_policies = 2

I am getting a behaviour, that when I run terraform first time, I get:

Error: Provider produced inconsistent result after apply

When applying changes to
module.<my-module>.module.lambda.aws_iam_role_policy_attachment.additional_many[0],
provider "registry.terraform.io/hashicorp/aws" produced an unexpected new
value: Root resource was present, but now absent.

However a second run added the SSM-related policy (that USED to be there initially) and no error is produced.

Is it something that can be improved so I do not get an error for the first run?

[antonbabenko]

Hi!

Please update the module version to the latest one (v2.17.0, see #195) where some improvements have been added to the way how IAM policies are attached to IAM role.

This should solve the issue you have experienced.

[github-actions]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.