Falco rule resource shows a priority change even if the resource isn't changed

[ukitazume]

When using sysdig_secure_rule_falco with priority = informational, terraform plan and apply shows ~ priority = "info" -> "informational" even if that rule doesn't change like here.

An execution plan has been generated and is shown below.
Resource actions are indicated with the following symbols:
  ~ update in-place

Terraform will perform the following actions:

  # sysdig_secure_rule_falco.foo will be updated in-place
  ~ resource "sysdig_secure_rule_falco" "foo" {
        append      = false
        condition   = "spawned_process and container and shell_procs and proc.tty != 0 and container_entrypoint"
        description = "this is other example of policy"
        id          = "20958"
        name        = "AOther example of Policy"
        output      = "A shell was spawned in a container with an attached terminal (user=%user.name %container.info shell=%proc.name parent=%proc.pname cmdline=%proc.cmdline terminal=%proc.tty container_id=%container.id image=%container.image.repository)"
      ~ priority    = "info" -> "informational"
        source      = "syscall"
        tags        = [
            "container",
            "shell",
            "mitre_execution",
        ]
        version     = 1
    }

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

[tembleking]

Thanks for reporting @ukitazume, the linked PR solves this problem, the field must be info instead of informational.

[ukitazume]

So quick!! thanks alot @tembleking