Skip to content
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

Adopt new logging patterns from tflog #24165

Closed
zhelding opened this issue Apr 8, 2022 · 4 comments
Closed

Adopt new logging patterns from tflog #24165

zhelding opened this issue Apr 8, 2022 · 4 comments
Labels
enhancement Requests to existing resources that expand the functionality or scope. stale Old or inactive issues managed by automation, if no further action taken these will get closed. sweeper Pertains to changes to or issues with the sweeper.

Comments

@zhelding
Copy link
Contributor

zhelding commented Apr 8, 2022

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment

Description

The tflog package provides functions for structured logging in lieu of using log.Printf("[LOG_LEVEL] some extended string"). This not only allows for more consistent writing of logging, but also allows us to designate a distinct subsystem of code that outputs logs at a separately set verbosity level.

For example: terraform-plugin-sdk/v2 by default uses tflog to set up TF_LOG_SDK and TF_LOG_PROVIDER when initializing tfserver; as such, these environmental variables are already supported by the provider. Similarly: we may be able to use tfsdklog to specify separate verbosity levels for provider, testing, and sweeper logs.

This is a sweeping change -- as it would alter every line of logging output across all files, but most of these can probably be replaced via a single complex sed command.

References

Relates: #22922

@zhelding zhelding added the enhancement Requests to existing resources that expand the functionality or scope. label Apr 8, 2022
@github-actions github-actions bot added the sweeper Pertains to changes to or issues with the sweeper. label Apr 8, 2022
@ewbankkit
Copy link
Contributor

We should consider adding an internal/logging package with useful wrapper/helper functions.
See e.g. hashicorp/terraform-plugin-framework#291.

@ewbankkit
Copy link
Contributor

Copy link

Marking this issue as stale due to inactivity. This helps our maintainers find and focus on the active issues. If this issue receives no comments in the next 30 days it will automatically be closed. Maintainers can also remove the stale label.

If this issue was automatically closed and you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thank you!

@github-actions github-actions bot added the stale Old or inactive issues managed by automation, if no further action taken these will get closed. label Apr 11, 2024
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale May 12, 2024
Copy link

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.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jun 12, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement Requests to existing resources that expand the functionality or scope. stale Old or inactive issues managed by automation, if no further action taken these will get closed. sweeper Pertains to changes to or issues with the sweeper.
Projects
None yet
Development

No branches or pull requests

2 participants