Kinesis application not keeping the order of record_columns

[ghost]

This issue was originally opened by @tfeuser123 as hashicorp/terraform#26943. It was migrated here as a result of the provider split. The original body of the issue is below.

---

Since Nov. 6 Friday, TFE is mixing column orders defined below. If you see code snippets below, HEADER_TYPE is the 1st column and AWS component (Kinesis Analytics) was keeping the same order as the terraform codes. But since Nov 6 (no changes), DATA_CD is the 1st column and all other columns are mixed up. So, we have to manual re-arrange the column orders from AWS console. More strangely, It works fine on local deploy with S3 backend (I mean it keeps the order). It is happening only for TFE deploy (TFE backend).

schema {
  record_columns {
    name     = "HEADER_TYPE"
    sql_type = "INTEGER"
  }

  record_columns {
    name     = "COL_2"
    sql_type = "INTEGER"
  }
  record_columns {
    name     = "DATA_CD"
    sql_type = "INTEGER"
  }

[ewbankkit]

@tfeuser123 Thanks for raising this issue.
#16005 changed the type of record_columns from TypeList to TypeSet hence the loss of column ordering.
I will correct this.

[ghost]

This has been released in version 3.18.0 of the Terraform AWS provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading.

For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template for triage. Thanks!

[ghost]

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 feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks!