-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Connection pooler not working when DB in VPC #151
Comments
Thank you for your feedback, looking into it! |
facing this same issue i have added more details in this link |
I am also facing this problem, is there a solution yet? |
Hello output "DB_HOSTNAME" {
value = strcontains(timescale_service.main.hostname, "forge") ? replace(timescale_service.main.hostname, "/([a-zA-Z\\d]+)(\\.)(.+)/", "$1-pooler$2$3") : timescale_service.main.hostname
description = "Probable hostname of the pooler of the DB"
}
output "DB_PORT" {
value = strcontains(timescale_service.main.hostname, "forge") ? 5432 : timescale_service.main.port
description = "Probable port of the connection pooler of the DB"
} Let me know if you see any errors |
any update on this? this is a pain point for our IaC |
Any update on this? I'm going to resort to string manipulation to hack this, but I'm sure that'll break at the worst possible time. Please fix. |
Hi!
First of all, thank you for working on this provider 😍
I tried the latest version to test the CRUD of the connection pooler, it works fine except when the DB is in a VPC
The Terraform output is
where the pooler hostname is
""
and the port doesn't reflect the Timescale UI information.The UI for the pooler shows hostname similar to the non-pooler one (only with
-pooler
inside) and a port 5432 instead of the one returned from terraformIf you need any other info let me know
The text was updated successfully, but these errors were encountered: