GET /deploy does not require token when tokens.txt is set

[lazzarello]

Running emmie service as NodePort, with SSH tunnel to localhost

curl -k https://localhost:30610/deploy returns JSON of all deployments in all namespaces when I have a token in tokens.txt

curl -k -X POST https://localhost:30610/deploy/leedev/0.0.10 returns the following log from the server in the pod

Token is NOT valid! =(

And returns the following headers to the client

*   Trying ::1...
* Connected to localhost (::1) port 30610 (#0)
* TLS 1.2 connection using TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
* Server certificate: something
> POST /deploy/leedev/0.0.10 HTTP/1.1
> Host: localhost:30610
> User-Agent: curl/7.49.1
> Accept: */*
> 
< HTTP/1.1 401 Unauthorized
< Date: Tue, 13 Dec 2016 03:34:04 GMT
< Content-Length: 0
< Content-Type: text/plain; charset=utf-8
< 
* Connection #0 to host localhost left intact

I'll get to a PR sometime tomorrow, I expect.

[stevesloka]

Yup looks like you found a bug. =(

I was working on the web ui piece and didn't properly secure the GET endpoint. The GET is defined here (https://github.com/upmc-enterprises/emmie/blob/master/emmie.go#L433) which called this: (https://github.com/upmc-enterprises/emmie/blob/master/deployments.go#L42).

You can comment out that route for now if that's easiest. I'll put up a PR in the morning to resolve this for you and get a new version pushed.