Commit Graph

3 Commits (cc2c826be6a7d96cc6ff2f2f18bbe2ba0ebc2ef7)

Author SHA1 Message Date
Mark Rushakoff 9bbe321d23 chore: serve swagger.json in development builds
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.
2019-03-09 12:42:44 -08:00
Mark Rushakoff e99c505287 refactor(http): only generate bindata asset for swagger.yml
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.
2019-03-04 09:40:00 -08:00
Chris Goller a11773838f feat(http): host swagger docs at /docs and /api/v2/swagger.json 2019-01-22 11:16:27 -06:00