super-linter: terrascan throws error on terraform moved blocks

Describe the bug

terraform 1.1 introduced a new feature - moved blocks. Read more at https://www.terraform.io/language/modules/develop/refactoring if you wish to understand them.

super-linter is failing when my code includes a moved block with error:

Unsupported block type; Blocks of type “moved” are not expected here.

It is the terrascan linter that is failing.

Expected behavior

moved blocks are valid syntax so terrascan should support them and not throw this error

Steps to Reproduce

1. Createa a new repository in github
2. Add a file main.tf with the following code:

resource "null_resource" "bar" {}

moved {
  from = null_resource.foo
  to = null_resource.bar
}

1. add a file .githib/workflows/workflow.yaml with:

name: demo
on:
  workflow_dispatch:

jobs:
  super-lint:
    name: Lint Code Base
    runs-on: ubuntu-latest
    steps:
      - name: Checkout code
        uses: actions/checkout@v2
      - name: Run Super-Linter
        uses: github/super-linter/slim@v4
        env:
          DEFAULT_BRANCH: main
          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

1. Manually trigger a run of workflow. It will (at the time of writing) fail with the error above.

You can see a repro of this problem at https://github.com/jamiet-msm/demo-super-linter-terrascan-issue/runs/6913423542?check_suite_focus=true#step:4:159

Additional context

Obviously the problem lies with terrascan but as the error is being raised via the use of super-linter I thought better to inform folks here of this issue. According to terrascan’s changelog moved blocks are supported since v1.14.0 (perhaps even earlier)

Closed issues: Blocks of type “moved” not supported https://github.com/accurics/terrascan/issues/1182

https://github.com/tenable/terrascan/blob/3ee999ad6f0936494a85501d66aebe312d0d1d0e/CHANGELOG.md#v1140-2022-04-01

and I believe super-linter is using a later version

➜ docker run -it --entrypoint bash ghcr.io/github/super-linter:slim-v4.9.4 -c "terrascan version"
version: v1.15.1

so I’m confused what the issue might be