Skip to content

When importing ovh_cloud_project it forces replacement #667

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

Closed
Saeden opened this issue Jun 18, 2024 · 3 comments · Fixed by #680
Closed

When importing ovh_cloud_project it forces replacement #667

Saeden opened this issue Jun 18, 2024 · 3 comments · Fixed by #680

Comments

@Saeden
Copy link

Saeden commented Jun 18, 2024

Describe the bug

We are trying to import an existing cloud project into terraform. We have the correct order number and the import is successful, however, when running terraform plan it shows that we have to replace the project and everything inside it because the plan and ovh_subsidiary objects are added. I assume this is not intended behaviour. The nodepools are also forced replacement because the kube_id and service_name are changed due to the replacement of the cloud_project.

Terraform Version

v1.6.6

OVH Terraform Provider Version

v0.45.0

Affected Resource(s)

Please list the resources as a list, for example:

  • ovh_cloud_project
  • ovh_cloud_project_kube
  • ovh_cloud_project_nodepool (multiple)

Terraform Configuration Files

[cluster.tar.gz](https://github.com/user-attachments/files/15888394/cluster.tar.gz)

Expected Behavior

The resources should be completed imported without forcing replacement.

Actual Behavior

After importing the resource it is forced to be replaced.

Steps to Reproduce

  1. terraform import ovh_cloud_project.prd_project ******(order_id)
  2. terraform plan
@amstuta
Copy link
Collaborator

amstuta commented Jul 8, 2024

Hello @Saeden, this is indeed not an expected behavior, we'll check quickly what can be done.

@amstuta
Copy link
Collaborator

amstuta commented Jul 8, 2024

A fix will be available in the next release (coming shortly), don't hesitate to open another issue if your problem persists.

@Saeden
Copy link
Author

Saeden commented Jul 19, 2024

Thanks so much! Sorry for my late reply, GH did not notify me that there were replies to this issue

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