Skip to content

Digger doesn't seem to detect changes that are about to be made #2035

@ChrisJBurns

Description

@ChrisJBurns

Digger only runs a plan on modification of TF files within a project, but sometimes there are changes to be made that aren't always changes that are made to the TF.

Take EKS add-ons for example, the add-on version is bumped automatically and if a plan is run, it is updated in-place. However this change was not driven by any TF change made in any files. Instead this is something that occurs automatically when there are new versions to use. Digger seems to miss this, and it is only ever caught if someone runs a plan against that project.

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

OpenTofu will perform the following actions:

# module.eks.module.k8s.module.eks.aws_eks_addon.this["aws-ebs-csi-driver"] will be updated in-place
~ resource "aws_eks_addon" "this" {
   ~ addon_version               = "v1.45.0-eksbuild.2" -> "v1.46.0-eksbuild.1"
     id                          = "eks:aws-ebs-csi-driver"
     tags                        = {}
     # (9 unchanged attributes hidden)

     # (1 unchanged block hidden)
 }

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions