Closed lpaturel closed 7 months ago
Hi @lpaturel , thanks for opening this issue.
It is quite difficult to pinpoint the issue with the configuration that you gave us, would you be able to have a reproducer with just a database instance and an associated user ?
Also, could you test with the provider version 0.40.0
? Just in case it is an issue that was resolved by a previous release.
Hello @amstuta , thanks for your answer.
We've update the provider version to 0.40.0
but nothing's changed on the "plan" output.
As of testing with a single database and associated user, I'll try to find how to reproduce the issue but I'm not sure if this can be done with newly created resources. I'll keep you posted whenever I have new information on how to reproduce the case.
Hello, little update here, it turns out that our tfstate may have had been corrupted due to some "manual" actions that we've attempted to correct. The number of nodes in the terraform plan was not accurate which has led to some misunderstanding as there was no error messaging but the replacing of resources... Closing this issue.
Describe the bug
As we are trying to add new users to our mongoDB instance (via ovh_cloud_project_database_mongodb_user), Terraform plans to replace the resources (even the database instance) instead of updating it in-place.
Terraform Version
/gitlab-org/terraform-images/releases/1.4:v1.0.0
OVH Terraform Provider Version
0.29
Affected Resource(s)
ovh_cloud_projectdatabase* Issue is found while trying to add users on MongoDB instance. We also encountered the issue while attempting to upgrade our PostgreSQL DB (from essential to business) and symptoms are the same with trying to replace instead of update.
Terraform Configuration Files
Debug Output
Expected Behavior
The resources should be "updated in-place" instead of "replaced".
Actual Behavior
If plan is applied, Terraform should destroy the resources before re-creating it.
Steps to Reproduce
our plan is launched as following with gitlab templates .terraform:build: &terraform_build stage: build script:
References
No ID as the issue is found inside our gitlab CI