Provider 3.39.0 doesn't support `extended_resource_collection_enabled` attribute, but documentation says it does about terraform-provider-datadog

[HantingZhang2]

Hello, you are most likely still using an older version of the provider. As the docs are generated from the schemas directly, I do not see how this can occur. I would suggest running terraform commands with TF_LOG=debug and see which provider version is being used for your module.

The deprecation message is added in the same pr that introduced the new parameter extended_resource_collection_enabled though, I can't reproduce it on my side.

+1 on double checking the provider version when using both parameters.

[skarimo]

Hello, you are most likely still using an older version of the provider. As the docs are generated from the schemas directly, I do not see how this can occur. I would suggest running terraform commands with TF_LOG=debug and see which provider version is being used for your module.

[eduardoasantana]

You were correct. The terraform workspace had a lock file locally pinning the Datadog provider to v3.38.0. Deleting this file and confirming it was on v3.39.0 made this issue go away. This lock file doesn't exist in source control, so that can explain the weird behavior of getting the error while also seeing a deprecation warning on a plan.

This issue can be closed.