fix: IPFS_LOG_LEVEL is actually deprecated, help text updated #10694
+23
−15
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The
ipfs log --help
text is updated to recommend the correct environment variable, and the debug logging check is more robust when checking if debug logging should be enabled.When running
ipfs log --help
I noticed two environment variables I was unfamiliar with. This PR updates every place where IPFS_LOG_LEVEL was used, to GOLOG_LOG_LEVEL, and IPFS_LOG_FMT to GOLOG_LOG_FMT, but does not completely "sunset" the deprecated environment variables.The
IPFS_LOG_LEVEL
environment variable was still in use in the code, so I think fully removing it at this point would be premature, let me know if you think otherwise.NOTE: these env vars were documented as deprecated in #8833