You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We're currently in the process of importing our existing Timescale databases into Terraform, as they were created manually a long time ago. As part of this, we get the password from the timescale_service resource and store it as a secret in AWS.
However, since these Timescale databases already existed and we're just trying to import them, the password value in the generated secret is null.
In your docs, you mention that the password is a one-time generated value:
It would be great if we could just provide a password ourselves to the timescale_service resource, which would also allow for password rotation (without recreating the entire DB instance). Would that be an option at all?
For reference, AWS DB instances also support providing a password yourself when creating an instance through Terraform.
The text was updated successfully, but these errors were encountered:
We're currently in the process of importing our existing Timescale databases into Terraform, as they were created manually a long time ago. As part of this, we get the password from the
timescale_service
resource and store it as a secret in AWS.However, since these Timescale databases already existed and we're just trying to import them, the password value in the generated secret is
null
.In your docs, you mention that the password is a one-time generated value:
It would be great if we could just provide a
password
ourselves to thetimescale_service
resource, which would also allow for password rotation (without recreating the entire DB instance). Would that be an option at all?For reference, AWS DB instances also support providing a password yourself when creating an instance through Terraform.
The text was updated successfully, but these errors were encountered: