Optional verbose logging for filestoreIntegrity.py #26
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 filestoreIntegrity.py script as currently written doesn't produce any output at all unless it finds a problem with an artifact. When running it against an Artifactory instance with 24 local repositories and over 275,000 artifacts, it just hangs silently at the command line with no indication that it's doing anything at all.
This PR adds a logger to the script and debug-level log messages for each repository and artifact that the script checks. This logging is not present by default, but is enabled by the
-vor--verbosearguments.