-
Notifications
You must be signed in to change notification settings - Fork 189
Provider defaults for parameters in provider version >= 1.4.1 #777
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
Comments
@wyardley we have a pre-release out with the fix: https://github.com/mongodb/terraform-provider-mongodbatlas/releases/tag/untagged-f6fcf34b988c94d3f95d would you be able to test it? We did pretty extensive testing (automated and manual) but it would be good to get a check. |
We decided to get the fix out the door @wyardley so please let us know if 1.4.2 works well for you. Closing this issue as complete. |
Thanks! And yes, after temporarily planning with all enabled again, we verified that the settings stay enabled. I didn’t check whether they’re set or unset under the hood, but seems to work now. |
@wyardley great news - thank you for sticking with us on this one. |
This is basically a continuation of #772 (issues with the changes in #741), but after the fix in #773, it seems as if the provider default is still forcing to false once the setting has been toggled at some point, even if it's currently set to
true
, for these newly added parameters.I haven't copied all the details / debugging info from #772, but I will close that again.
Terraform CLI and Terraform MongoDB Atlas Provider Version
Terraform Configuration File
Steps to Reproduce
Expected Behavior
Actual Behavior
Debug Output
Crash Output
Additional Context
References
The text was updated successfully, but these errors were encountered: