Skip to content

ingress_rules rule description show changes after every terraform apply starting from 3.23.1 release #324

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
gartemiev opened this issue Nov 8, 2022 · 4 comments · Fixed by #325

Comments

@gartemiev
Copy link

Starting from 3.23.1 release of module I constantly get updating of description for ingress_rules in security group:

  # module.atlantis_prod.module.efs_sg[0].module.sg.aws_security_group_rule.ingress_rules[0] will be updated in-place
  ~ resource "aws_security_group_rule" "ingress_rules" {
      + description       = "NFS/EFS"
        id                = "sgrule-3597383068"
@amontalban
Copy link
Contributor

I'm having the same issue:

Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
  ~ update in-place

Terraform will perform the following actions:

  # module.efs_sg[0].module.sg.aws_security_group_rule.ingress_rules[0] will be updated in-place
!   resource "aws_security_group_rule" "ingress_rules" {
+       description       = "NFS/EFS"
        id                = "sgrule-2398660193"
        # (9 unchanged attributes hidden)
    }

Plan: 0 to add, 1 to change, 0 to destroy.

@gartemiev
Copy link
Author

@bryantbiggs @antonbabenko , any chance to fix this?

@dynamike
Copy link
Member

Hi! I think I've figured out what's going on here. I'll have a PR with the fixes next week.

@github-actions
Copy link

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.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Dec 17, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
3 participants