Nikhil Singh

@MikiLoz92 Can you share the project ID so that I can check the reason for the deletion not happening and any error generated for that in our backend logs. Also...

I cannot repro this at my end and everything works perfectly during creation and termination. @MikiLoz92 Once you have the logs, it will help us a lot.

@MikiLoz92 Yes, there should be nothing in the project which is mapped to the VPC. It does not matters if the resource is launched using terraform or from UI or...

@MikiLoz92 @AlexRex Please share your Project ID over email [email protected] since this is a public platform and I would not want you to share your Project ID here so I...

@MikiLoz92 @leynebe @AlexRex I can repro this. This happens in a condition where the cluster has been destroyed without destroying the network container. I guess the problem here is the...

@leynebe I can see that the below block is in use - ```js lifecycle { prevent_destroy = true } ``` Therefore, do you explicitly set it to `false` before termination....

After many repros and different configurations, I am certain that the problem is using `-target=` to explicitly delete the cluster and it is unable to set the correct values to...

@nathankodilla The project rename is an Atlas UI feature and there is no public API to achieve this. Therefore, terraform is applying the changes in correct manner as it does...

@piotrgwiazda The first 401 and then 200 response seen is due to the digest auth mechanism used by the Atlas API. However, please confirm if you are still facing this...

@in4mer This is not an issue, but needs some changes in the way terraform configuration has to be written for NVMe clusters. As per the MongoDB Atlas Cluster [API](https://docs.atlas.mongodb.com/reference/api/clusters-create-one/) for...