Skip to content

fix(terraform): use key_schema for DynamoDB GSIs#316

Merged
edersonbrilhante merged 1 commit into
mainfrom
fix-dynamodb-key-schema
Jun 5, 2026
Merged

fix(terraform): use key_schema for DynamoDB GSIs#316
edersonbrilhante merged 1 commit into
mainfrom
fix-dynamodb-key-schema

Conversation

@edersonbrilhante

Copy link
Copy Markdown
Member

Description

Updates the GitHub global lock DynamoDB table configuration to replace deprecated hash_key arguments on global secondary indexes with key_schema blocks.

This keeps the existing GSI partition keys unchanged (workflow_run_id and workflow_run_attempt) while aligning the module with the AWS provider 6.x DynamoDB schema. The table-level primary key remains hash_key = "lock_id" because key_schema is only supported for the GSI configuration in this provider schema.

Technical reference: https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/dynamodb_table.html

Type of Change

  • Bug Fix
  • New Feature
  • Breaking Change
  • Refactor
  • Documentation
  • Other (please describe)

Checklist

  • I have read the contributing guidelines
  • Existing issues have been referenced (where applicable)
  • I have verified this change is not present in other open pull requests
  • Functionality is documented
  • All code style checks pass
  • New code contribution is covered by automated tests
  • All new and existing tests pass

@edersonbrilhante edersonbrilhante force-pushed the fix-dynamodb-key-schema branch from 475b36a to 2019bf1 Compare June 5, 2026 10:01
@edersonbrilhante edersonbrilhante merged commit 9f4df99 into main Jun 5, 2026
5 checks passed
@edersonbrilhante edersonbrilhante deleted the fix-dynamodb-key-schema branch June 5, 2026 11:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants