Docs: don't outright discard the legacy way of logging as sometimes, it's the only solution

[mlcdf]

Does this documenation exist?

• This is new documentation
• This is an enhancement to existing documentation

Where would you expect to find this documentation?

• On terraform.io
• In the GoDoc for this module
• In this repo as a markdown file
• Somewhere else

Details

The following docs regarding logging are a bit misleading:

• https://developer.hashicorp.com/terraform/tutorials/providers-plugin-framework/providers-plugin-framework-logging
• https://developer.hashicorp.com/terraform/plugin/log/writing

They either suggest that tflog is the only way to log or describe log.Prinftas the legacy way.

But if you want to log in a hook that does not pass a context.Context, the legacy way is the only way to do so.

Some hooks that don't pass a context:

• StateFunc
• ValidateDiagFunc
• DiffSuppressFunc

Description

Different wording explaining that in some cases, using the legacy way of logging is OK and the only way to do so.

(I'm a terraform newbie so I apologize if I missed something)

[bendbennett]

Hi @mlcdf 👋

Thank you for raising this issue. As this issue relates specifically to functions that are available within terraform-plugin-sdk I am going to transfer the issue to that repository and we will review updating the documentation for the SDK.

[mlcdf]

Thanks :)

[github-actions]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.