Consider Enabling TF_LOG_PROVIDER to Set Root Provider (and Root SDK?) Logger Levels

[bflad]

terraform-plugin-log version

v0.4.0

Use cases

terraform-plugin-sdk/v2@v2.18.0 enables the acceptance testing framework to passthrough the TF_LOG_CORE and TF_LOG_PROVIDER environment variables to its underlying terraform-exec handling and ultimately Terraform CLI. Acceptance testing is a little strange in terms of logging because the provider "under test" is being executed directly with its logs being controlled by the testing framework, rather than production where logs flow always through Terraform CLI. This means that setting just TF_LOG_PROVIDER during testing does not have the desired effect of controlling the provider under test logs anymore (it does, however, control external providers that still log through Terraform CLI).

Attempted solutions

TF_LOG_CORE=WARN TF_LOG_PROVIDER_XXX=TRACE go test

Proposal

Introduce additional environment variable handling into the root loggers that would allow provider logging to work the same in production and acceptance testing.

The following behaviors could be a good starting point:

TF_LOG_PROVIDER	TF_LOG_PROVIDER_XXX	TF_LOG_SDK	Provider Log Level	SDK Log Level
(none)	(none)	(none)	OFF	OFF
DEBUG	(none)	(none)	DEBUG	DEBUG
(none)	DEBUG	(none)	DEBUG	OFF
(none)	(none)	DEBUG	OFF	DEBUG
(none)	TRACE	DEBUG	TRACE	DEBUG
TRACE	DEBUG	(none)	DEBUG	TRACE
TRACE	(none)	DEBUG	TRACE	DEBUG
TRACE	DEBUG	INFO	DEBUG	INFO

References

• Allow TF_LOG/TF_LOG_CORE/TF_LOG_PROVIDER to be set correctly in Acceptance Tests terraform-plugin-sdk#992