Terraform 路由 table 与 VPC 端点的关联
Terraform route table association with VPC Endpoint
将 vpc 端点关联到路由时,我在使用 terraform(云)时遇到问题
VPC 端点
resource "aws_vpc_endpoint" "s3_endpoint_gateway" {
vpc_id = aws_vpc.edcelvistacom_vpc.id
service_name = "com.amazonaws.${var.region}.s3"
tags = {
"Name" = "VPC Endpoint S3 - for Private Resources"
"Project" = "edcelvistacom"
"Env" = "Production"
}
}
路线关联
resource "aws_vpc_endpoint_route_table_association" "application" {
count = length(var.availability_zones)
route_table_id = element(aws_route_table.application.*.id, count.index)
vpc_endpoint_id = aws_vpc_endpoint.s3_endpoint_gateway.id
}
错误:
Error: Provider produced inconsistent result after apply
When applying changes to
module.networking.aws_vpc_endpoint_route_table_association.application[1],
provider "registry.terraform.io/hashicorp/aws" produced an unexpected new
value: Root resource was present, but now absent.
This is a bug in the provider, which should be reported in the provider's own
issue tracker.
aws 2.70
很老了。此问题已在 aws 3.36
中 reported on github and it seems it has been fixed。因此,我会尝试使用最新版本 3.40
,如果错误仍然存在,则使用详细信息创建一个新的 github 问题。
将 vpc 端点关联到路由时,我在使用 terraform(云)时遇到问题
VPC 端点
resource "aws_vpc_endpoint" "s3_endpoint_gateway" {
vpc_id = aws_vpc.edcelvistacom_vpc.id
service_name = "com.amazonaws.${var.region}.s3"
tags = {
"Name" = "VPC Endpoint S3 - for Private Resources"
"Project" = "edcelvistacom"
"Env" = "Production"
}
}
路线关联
resource "aws_vpc_endpoint_route_table_association" "application" {
count = length(var.availability_zones)
route_table_id = element(aws_route_table.application.*.id, count.index)
vpc_endpoint_id = aws_vpc_endpoint.s3_endpoint_gateway.id
}
错误:
Error: Provider produced inconsistent result after apply
When applying changes to
module.networking.aws_vpc_endpoint_route_table_association.application[1],
provider "registry.terraform.io/hashicorp/aws" produced an unexpected new
value: Root resource was present, but now absent.
This is a bug in the provider, which should be reported in the provider's own
issue tracker.
aws 2.70
很老了。此问题已在 aws 3.36
中 reported on github and it seems it has been fixed。因此,我会尝试使用最新版本 3.40
,如果错误仍然存在,则使用详细信息创建一个新的 github 问题。