search

timescale / terraform-provider-timescale

Timescale Cloud Terraform Provider
Apache License 2.0
18 stars 2 forks source link

VPC peering connection returns incorrect ID #158

Closed jkrall closed 6 months ago

jkrall commented 7 months ago

(possibly related to https://github.com/timescale/terraform-provider-timescale/issues/131)

Having manually setup a peering-connection in the timescale UI, I am getting the following data from terraform in the peering_connections array:

            "peering_connections": [
              {
                "error_message": "",
                "id": 3011,
                "peer_vpc": {
                  "account_id": "...hidden...",
                  "cidr": "172.16.0.0/16",
                  "id": "...hidden...",
                  "region_code": "us-east-2"
                },
                "status": "ACTIVE",
                "vpc_id": "...hidden..."
              }
            ],

Note that the id being returned is a numeric number, rather than the AWS id of the peering connection, ala pcx-...

This prevents using terraform to reference the peering connection and configure an aws_route to refer to the peering connection.

Khyme commented 6 months ago

Fixed with version v1.9.0 ! the pcx- value is in the provisioned_id field (might need a refresh)