Skip to content
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

Bug: timescale_service resource not propagating its attributes #180

Open
pieeri opened this issue Mar 22, 2024 · 2 comments
Open

Bug: timescale_service resource not propagating its attributes #180

pieeri opened this issue Mar 22, 2024 · 2 comments

Comments

@pieeri
Copy link

pieeri commented Mar 22, 2024

Hi Timescale team,

We're currently deploying TS services thanks to your Terraform provider (v1.9.0) and are eager to integrate your provider with our multi tenant client deployments.

We have managed to programmatically create a Timescale VPC and accept automatically the Timescale peering connection within our AWS cloud, while launching a service and associating it with an internal DNS record (Route53).

While this works admirably, we reset the instance password through the Timescale web UI and ran into a situation where the password provided by the timescale_service resource didn't refresh, despite resync'ing / refreshing our Terraform plan.

To allow our application to connect, we had to destroy such a Timescale service and recreate a new one from scratch (and we ran into #177 as well, where Terraform couldn't recognise that it was removed).

Please let us know if you need more information to investigate the issue. Many thanks in advance!

@pieeri pieeri changed the title Bug: timescale_service resource not propagating attribute Bug: timescale_service resource not propagating attribute Mar 22, 2024
@pieeri pieeri changed the title Bug: timescale_service resource not propagating attribute Bug: timescale_service resource not propagating its attributes Mar 22, 2024
@Khyme
Copy link
Contributor

Khyme commented Mar 22, 2024

Thank you for your feedback.
I'm investigate as I know we labeled password a sensitive field and terraform internals might have a specific dynamic for it that we did not implement yet.

@fatima-kscope
Copy link

@Khyme I'm storing the timescale password in a secrets manager when terraform is run. It becomes null in the secrets manager everytime I run terraform, most likely because of this issue. Also, weirdly, only seeing this in one deployment. Is there a workaround/fix in progress?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants