Logs are broken about arsenal

This means that the tests did not catch a call to the validateAuthConfig function. Fixing the way it's called should be enough.

[romfreiman]

can you elaborate please? I actually did nothing on S3 side. Just rebuild the docker image.

As you can see in https://github.com/scality/Arsenal/pull/314/files#diff-3730f90bb19d3b3646a968c2a4dddbdeL169 ; a project-wide change was made to werelogs to fix an insidious configuration bug; and led to a change in the API of a few common/library functions.

I may have missed some calls to this library in various projects, due to lack of automated testing and attention. If you find any, you may fix it following the method used in the same PR: https://github.com/scality/Arsenal/pull/314/files#diff-a400b2bf757d4e597747b3bd4a2105ddR33

Alternatively, you may want to make sure you installed the proper versions of arsenal and werelogs, by removing your node_modules, and re-installing the dependencies (since we know npm doesn't handle git branches very well)

After testing it out, I see it working (of course, you may need to rm -rf node_modules; then npm install ; before this works, as I described earlier).
That being said, I found out an obsolete piece of code in the S3 repository at https://github.com/scality/S3/blob/master/dataserver.js#L15 (The config bit about the logs in this line is not taken into account by Arsenal, so it might as well be removed). I'll leave the S3 team to handle this.

Then, Can we close this issue ?

[romfreiman]

Sure. Closing.