The inclusion of SHA1 and MD5 output in the request logs really have no practical use for every day logs and are of minor interest outside of debugging.
This change will push these values to debug only status, meaning they will only display when logs are set to debug or more verbose.
What areas of the application does this impact?
This impacts the custom access log
[-] I have updated/added unit and integration tests that prove my fix is effective or that my feature works
[x] New and existing unit and int tests pass locally and remotely with my changes
[x ] I have removed unnecessary/dead code and imports in files I have changed
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[-] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[-] I have cleaned up integration tests by doing one or more of the following:
de-duped, consolidated, removed dead int tests
transformed applicable int tests into unit tests
refactored to reduce number of system state resets by updating fixtures (use-fixtures :each (ingest/reset-fixture {})) to be :once instead of :each
Overview
The inclusion of SHA1 and MD5 output in the request logs really have no practical use for every day logs and are of minor interest outside of debugging.
This change will push these values to debug only status, meaning they will only display when logs are set to debug or more verbose.
What areas of the application does this impact?
This impacts the custom access log