* chore: Remove several instances of WithLogger
* chore: unexport Logger fields
* chore: unexport some more Logger fields
* chore: go fmt
chore: fix test
chore: s/logger/log
chore: fix test
chore: revert http.Handler.Handler constructor initialization
* refactor: integrate review feedback, fix all test nop loggers
* refactor: capitalize all log messages
* refactor: rename two logger to log
In a development build (i.e. does not have the assets build tag), the
first request to GET /api/v2/swagger.json will produce log output like:
INFLUXDB_VALID_SWAGGER_PATH not set; falling back to checking relative paths {"log_id": "0E4I7Dkl000", "service": "swagger-loader"}
Successfully loaded swagger.yml {"log_id": "0E4I7Dkl000", "service": "swagger-loader", "path": "/.../influxdb/http/swagger.yml"}
There is no such log line in production builds.
But now both builds correctly serve swagger.json, instead of just
production builds.
The previous "." argument with "-ignore go" accidentally matched
README.md and Makefile too, neither of which we care to actually include
as assets.
Now we just explicitly include swagger.yml. It's simple enough to add
another file to the go:generate line if and when we need it.
Jonathan A. Sternberg
Jacob Marble
Kelvin Wang
Mark Rushakoff
Chris Goller