Hi,
Is there a particular reason why upgrading an existing Mongo 3.2 Server instance to 3.6, using the “EnableMongo” capability, results in Terraform needing to rebuild the entire instance?
We’ve been using Cosmos and Terraform for a while in our environments, but we would like to upgrade to Mongo 3.6 api without destroying our production data.
The portal seems to support doing it, but we’d like to keep it under terraform control.
Would be good to understand if there’s a limitation before opening up a feature / bug on the provider in github.
Thanks
Paul