-
Notifications
You must be signed in to change notification settings - Fork 24
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
Error: error while fetching dbaas cluster xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx: is not a valid PoolMode #681
Comments
Can you share the cluster in the tf plan? Between what versions is the upgrade? |
From version 6.3.1 to 6.5.6. Here's the database resource:
|
@mway-niels we investigated and the issue is not from our side (Terraform provider), it is from the DBaaS API, we discussed with our colleagues from the DBaaS team and they will come up with a solution for this. If you want to find out more information about this, such as when it will be solved or other details, please send an e-mail to one of the addresses listed here: https://docs.ionos.com/support/general-information/contact-information. We will close this issue since there is nothing to do on our side. L.E: I will reopen the issue since we want to make sure that the fix from DBaaS team will actually solve this. Thank you! |
Problem was fixed on some of the clusters, not all. You can try to upgrade and see what happens. |
Yes, it's working as expected now. Thank you for your support. |
Description
Upgrading the Terraform provider is not possible if the state contains old managed PostgreSQL clusters.
terraform plan
returns the error messageError: error while fetching dbaas cluster xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx: is not a valid PoolMode
on old managed PostgreSQL clusters.Expected behavior
When upgrading the IONOS Terraform provider, new API properties/fields shouldn't cause
terraform plan/apply
to return an error.Environment
Terraform version:
Provider version:
OS:
How to Reproduce
As I'm not able to create a managed PostgreSQL using the old IONOS API, I'm not sure how to reproduce this bug with new configurations.
Error and Debug Output
The text was updated successfully, but these errors were encountered: