Question

我在Terraform中有以下配置

resource "aws_dynamodb_table" "scanner" {
name = "scanner"
read_capacity = 2
write_capacity = 1
hash_key = "public_ip"
attribute {
    name = "public_ip"
    type = "S"
}
attribute {
    name = "region"
    type = "S"
}
attribute {
    name = "account_id"
    type = "N"
}
global_secondary_index {
    name = "cleanup-index"
    hash_key = "account_id"
    range_key = "region"
    read_capacity = 1
    write_capacity = 1
    projection_type = "INCLUDE"
    non_key_attributes = ["vpc_id", "instance_id", "integration_id", "private_ip"]
}
}

直到我从Terraform 0.7.13升级到0.9.6之前，它一直很完美。从那以后，Terraform每次尝试重新创建索引：

~ aws_dynamodb_table.scanner
global_secondary_index.3508752412.hash_key:             "" => "account_id"
global_secondary_index.3508752412.name:                 "" => "cleanup-index"
global_secondary_index.3508752412.non_key_attributes.#: "0" => "4"
global_secondary_index.3508752412.non_key_attributes.0: "" => "vpc_id"
global_secondary_index.3508752412.non_key_attributes.1: "" => "instance_id"
global_secondary_index.3508752412.non_key_attributes.2: "" => "integration_id"
global_secondary_index.3508752412.non_key_attributes.3: "" => "private_ip"
global_secondary_index.3508752412.projection_type:      "" => "INCLUDE"
global_secondary_index.3508752412.range_key:            "" => "region"
global_secondary_index.3508752412.read_capacity:        "" => "1"
global_secondary_index.3508752412.write_capacity:       "" => "1"
global_secondary_index.3860163270.hash_key:             "account_id" => ""
global_secondary_index.3860163270.name:                 "cleanup-index" => ""
global_secondary_index.3860163270.non_key_attributes.#: "4" => "0"
global_secondary_index.3860163270.non_key_attributes.0: "vpc_id" => ""
global_secondary_index.3860163270.non_key_attributes.1: "instance_id" => ""
global_secondary_index.3860163270.non_key_attributes.2: "private_ip" => ""
global_secondary_index.3860163270.non_key_attributes.3: "integration_id" => ""
global_secondary_index.3860163270.projection_type:      "INCLUDE" => ""
global_secondary_index.3860163270.range_key:            "region" => ""
global_secondary_index.3860163270.read_capacity:        "1" => "0"
global_secondary_index.3860163270.write_capacity:       "1" => "0"

Terraform在他们的doc中说： DynamoDB API期望在创建或更新GSI / LSI或创建初始表时传递属性结构（名称和类型）。在这些情况下，它希望提供哈希/范围键;因为这些可以在很多地方重复使用（即表的范围键可以是一个或多个GSI的一部分），它们存储在表对象上以防止重复并提高一致性。如果你在这里添加未在这些场景中使用的属性，它可能会导致计划中的无限循环。但我不认为我的配置与此相关。有类似的经历吗？我怀疑与this的关系。谢谢！

Answer 1

有时，底层提供者API会对Terraform提交的数据进行规范化或重组，以便在回读时数据不同。

这似乎就是这种情况的一个例子。在配置中，non_key_attributes列为["vpc_id", "instance_id", "integration_id", "private_ip"]，但它们是以["vpc_id", "instance_id", "private_ip", "integration_id"]的形式从API返回的。

Terraform中的一个错误是它没有将这两个视为等效，如果确实（因为它看起来）排序不敏感，并且DynamoDB API可以以不同于提交的顺序返回它们。

作为一种解决方法，直到修复了这个错误，它可能会重新排序配置中的列表以匹配API返回的内容，这应该会导致Terraform不再看到差异。只要API以一致的一致顺序将列表从一个请求返回到下一个请求，这应该可以正常工作。

Terraform DynamoDB索引循环

1 个答案: