-
Notifications
You must be signed in to change notification settings - Fork 187
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
Regression in 1.8.0: mongodbatlas_third_party_integration marks "type" attribute as deprecated #1032
Comments
thanks @legal90 we are investigating and will revert back shortly. appreciate all the rapid feedback here (as always) 👍🏽 |
@legal90 Will address issue in v1.8.1 engineering ticket INTMDB-556 in place to track |
@legal90 v1.8.1 has been published to the Terraform Public Registry! take a spin and let us know if you need anything else. |
Thank you, @Zuhairahmed ! I confirm that the deprecation message is gone now. The provider v1.8.1 works as expected 👍 |
Terraform CLI and Terraform MongoDB Atlas Provider Version
Terraform Configuration File
Steps to Reproduce
terraform apply
Expected Behavior
No warnings or deprecations are raised.
Actual Behavior
Additional Context
This was introduced in 1.8.0: https://github.com/mongodb/terraform-provider-mongodbatlas/pull/1018/files/24eef4010c2f791f3fd544a80f8bbebfbfa794c4#diff-8e65feb4edd9f3cade8198fe8f62bcbb4dfb59ce8ec2ea22f8c31ba7f7ad04b8
As I said in the comment there, the field
Deprecated
should not be used in that case, as it deprecates the entiretype
attribute of this resource. Instead, you need to use a custom function forValidateDiagFunc
field. That custom function should return a warning when the value oftype
attribute is set to"NEW_RELIC"
or"FLOWDOCK"
.References
ValidateDiagFunc
schema doc: https://developer.hashicorp.com/terraform/plugin/sdkv2/schemas/schema-behaviors#validatediagfuncThe text was updated successfully, but these errors were encountered: