aws_keyspaces_table specify clustering column order

[jack-at-circle]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Description

Using the aws_keyspaces_table resource, I can't specify the order of clustering columns. This breaks my current table schema when migrating from Cassandra to Keyspaces. I've tried changing the order of declaration within the schema_definition to no effect.

New or Affected Resource(s)

• aws_keyspaces_table

Potential Terraform Configuration

Either, respect the order of declaration as an implicit order for the clustering columns, or allow explicit oder declaration like the following

resource "aws_keyspaces_table" "table" {
  keyspace_name = aws_keyspaces_keyspace.example.name
  table_name    = "my_table"

  schema_definition {
    column {
      name = "partition_key"
      type = "ASCII"
    }

    column {
      name = "cluster_key_0"
      type = "ASCII"
    }

    column {
      name = "cluster_key_1"
      type = "ASCII"
    }

    partition_key {
      name = "partition_key"
    }

    clustering_key {
      name = "cluster_key_0"
      order_by = "DESC"
      position = 0
    }

    clustering_key {
      name = "cluster_key_1"
      order_by = "ASC"
      position = 1
    }
  }

  depends_on = [aws_keyspaces_keyspace.keyspace]
}

References

This line may be the problem

terraform-provider-aws/internal/service/keyspaces/table.go

Line 167 in 64daad7

Type: schema.TypeSet,

[jack-at-circle]

Comment: I found a crude work around for now by changing column names until they happened to be created in the order I needed

[github-actions]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.