Open eddyfussel opened 2 weeks ago
Hello @eddyfussel, I encountered the same issue myself when developing it, and had some issues fixing it. IIRC, the code handling the timescale peering connection doesn't surface the provisioned-id so I think it needs wider code change on our end I didn't have the opportunity to, so released that half way done. I'm sorry for the inconvenience.
As for when this might be fixed, I think this provider will not see some love again until Q3/4.
Hi, I'm using this provider to create a timescale database for testing the saas product. Since we would like to use a private endpoint, I use the
timescale_peering_connection
resource to peer with our vpc.If I place my
aws_vpc_peering_connection_accepter
directly next to thetimescale_peering_connection
I can directly use theprovisioned_id
as an input for thevpc_peering_connection_id
Here is some example code
However this is not working, as get following error that indicates, that the
provisioned-id
is null.To proof that I directly pulled the state from terraform by executing
terraform console
Executing the
apply
again I get a change on the resource and the code starts working.I would expect this to work, as the resource
aws_vpc_peering_connection
from aws to create a vpc peering between multiple vpcs is waiting until there is thepcx-..
available.I've tried to update my code to add a delay, unfortunately that wasn't successful.
I also have here a log file to see the commands I've executed: bug_timescale_provider_retracted.txt
Thanks in advance for any feedback, idea or help.
BR eddyfussel