Receiving error "Missing the key LockID in the item" from github-action-atmos-terraform-plan

[Maciej-Gadomski]

Hello, during execution of github-action-atmos-terraform-plan, I receive "Missing the key LockID in the item" error message which comes from github-action-terraform-plan-storage. Plan file was successfully stored in s3 and then dynamo error appear. Any ideas?

name: Plan Atmos Component
uses: cloudposse/github-action-atmos-terraform-plan@v4
with:
    component: ${{ matrix.component }}
    stack: ${{ matrix.stack }}
    atmos-config-path: .
    atmos-version: 1.165.2

[milldr]

This error is likely an indicator that the DynamoDB table is misconfigured. Do you have integrations.github.gitops configured in your atmos config?

See these docs for reference: https://atmos.tools/integrations/github-actions/#atmos-configuration

[Maciej-Gadomski]

yes i have it configured.

[milldr]

can you share what you have please? And can you also share your DynamoDB table configuration itself?

[Maciej-Gadomski]

integrations:
  github:
    gitops:
      terraform-version: 1.8.5
      infracost-enabled: false
      artifact-storage:
        region: eu-central-1
        bucket: {bucket_name}
        table: {table_name}
        role: {role_arn}
        metadata-repository-type: dynamo
        planRepositoryType: s3
      role:
        plan: {role_arn}
        apply: {role_arn}
      matrix:
        sort-by: .stack_slug
        group-by: .stack_slug | split("-") | [.[0], .[2]] | join("-")

[milldr]

You will need to create the global secondary index "pr-createdAt-index" so that the action can query the latest plan file for a given PR.

Please see this configuration for reference: https://atmos.tools/integrations/github-actions/#dynamodb-table

[Maciej-Gadomski]

Can the "global secondary index" parameter be included if my bucket and DynamoDB table weren't created by Atmos?

[milldr]

Yes you can configure them however you like, but we of course prefer Atmos