-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
force mongoenabled for mongo34 #13757
Conversation
koikonom
commented
Oct 15, 2021
- Throw error if there is a missing capability when enabling mongo
- update docs
When we enable capability `MongoDBv3.4` azure also sets `EnableMongo`. As a result next time terraform runs it sees both capabilities enabled, and since only `MongoDBv3.4` is enabled in the config it will try to change the capabiltiies to match what it has in the config. In this case it means destroying the database and building it again, since the `capabilities` setting has `ForceNew` set to true. This commit uses a CustomizeDiff function to enforce this during plan.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @koikonom - other then one comment this LGTM 🌿
Co-authored-by: kt <[email protected]>
This functionality has been released in v2.82.0 of the Terraform Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you! |
I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active contributions. |