The catalogit-api from turnerlabs

catalogit-api's People

Contributors

Stargazers

Watchers

catalogit-api's Issues

add authentication

all rest endpoints need to be authenticated
use auth server to implement authentication

Underscores kill the server

Underscores seem to cause catalogit to throw up on itself. Let's fix this.

Trying to POST the same (name, version) tuple yields a non-obvious 422 error

When trying to POST to /v1/containers with an already existing (name, version) tuple, CatalogIt will barf all over itself and return a 422 to the client with nary any indication as to what really went on:

error   10-May-2017 15:08:28    * About to connect() to catalogit.services.dmtio.net port 80 (#0)
error   10-May-2017 15:08:28    *   Trying 10.61.6.71... connected
error   10-May-2017 15:08:28    > POST /v1/containers HTTP/1.1
error   10-May-2017 15:08:28    > User-Agent: curl/7.22.0 (x86_64-pc-linux-gnu) libcurl/7.22.0 OpenSSL/1.0.1 zlib/1.2.3.4 libidn/1.23 librtmp/2.3
error   10-May-2017 15:08:28    > Host: catalogit.services.dmtio.net
error   10-May-2017 15:08:28    > Accept: */*
error   10-May-2017 15:08:28    > Content-Type: application/json
error   10-May-2017 15:08:28    > Content-Length: 202
error   10-May-2017 15:08:28    > 
error   10-May-2017 15:08:28    } [data not shown]
error   10-May-2017 15:08:28    * upload completely sent off: 202out of 202 bytes
error   10-May-2017 15:08:28    * The requested URL returned error: 422
error   10-May-2017 15:08:28    * Closing connection #0
error   10-May-2017 15:08:28    [ERROR] Posting image to CatalogIt failed.

This makes debugging, e.g., Bamboo build failures kind of a pain when considering CatalogIt itself as a black box.