Open davekonopka opened 2 months ago
It seems like this issue may be pointing to the same problem: #495
I'm also encountering this same issue.
This issue has been automatically marked as stale because it has been open 30 days with no activity. Remove stale label or comment or this issue will be closed in 10 days
Description
We're running into an issue with the
iam-assumable-role
submodule showing changes foraws_iam_role
resourceassume_role_policy
field when no changes exist. This seems to trigger multipledata
resource reads too creating a lot of plan noise.One thing I noticed is that the list of Principals is reversed between the
data aws_iam_policy_document
and theresource "aws_iam_role"
field. Could this be the issue?⚠️ Note
Before you submit an issue, please perform the following first:
.terraform
directory (! ONLY if state is stored remotely, which hopefully you are following that best practice!):rm -rf .terraform/
terraform init
Versions
Module version 5.44.0
Terraform version: v1.9.5
Provider version(s):
provider registry.terraform.io/hashicorp/aws v5.64.0
provider registry.terraform.io/hashicorp/cloudinit v2.3.4
provider registry.terraform.io/hashicorp/external v2.3.3
provider registry.terraform.io/hashicorp/helm v2.14.0
provider registry.terraform.io/hashicorp/null v3.2.2
provider registry.terraform.io/hashicorp/time v0.12.0
provider registry.terraform.io/hashicorp/tls v4.0.5
Reproduction Code [Required]
Steps to reproduce the behavior:
No. Yes.Expected behavior
No changes show for a plan when no changes exist.
Actual behavior
Changes show for
assume_role_policy
on the role and multipledata
resources load but no real changes exists.Terminal Output Screenshot(s)
Additional context
Example plan output
We use this module within one of our own modules. That's why the resources show an extra layer. My example removes this layer and still has the issue.