-
Notifications
You must be signed in to change notification settings - Fork 159
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
d/workspace external_id #268
Comments
Hi! As the messages says, more details this deprecation can be found in the changelog:
So - not necessarily the next release, but a release on or past the specified date. I do empathize with any annoyance of the deprecation warning not able to be resolved in any way, and hope to remove it ASAP - but this is a common workaround for the limitations of the SDK at the moment and was used from the start of this long migration for workspace IDs. We intend to see it through for at least this particular set of changes. Thanks! |
Yeah, it's a bit misleading with data resource as it's bot using that argument in the code itself. |
I agree completely 👍 In my own opinion, I wouldn't use this schema mechanism in the future even if the SDK still doesn't allow for warnings at-access when a configuration is actually evaluated; it just gets too noisy. (More thoughts here) Here's the issue tracking this ability, if you're curious: hashicorp/terraform#7569 |
Indeed, cheers and thanks for related discussions 👍 . Wanted to check first before opening a PR and trying to remove those here 🙂 |
Is there any reason to keep this warning https://github.com/hashicorp/terraform-provider-tfe/blob/master/tfe/data_source_workspace.go#L13 ? Assuming in the next release we can remove this from r/ d/ resources?
The text was updated successfully, but these errors were encountered: