v0.0.0-1607021651

fix worker memory test

looks like we changed the semantics away from using garden's "total usage toward
limit" number and instead used the recommended computation from the linux kernel
documentation.

Signed-off-by: Jamie Klassen <[email protected]>

v0.0.0-1602174882

First attempt at showing memory

We seem to hit an int overflow somewhere when printing out the data sizes, and
the first columen has a tendency to waste a lot of screen space.

concourse/concourse#6140

Signed-off-by: Jamie Klassen <[email protected]>
Co-authored-by: Zoe Tian <[email protected]>

v0.0.0-1599763998

determine ssl files from web pod

the switch statements are really ugly

next up is to see about passing a custom dialer to the pq driver which will
handle ssl on our behalf -- so that we don't need to write temp files!

concourse/concourse#6040

Signed-off-by: Jamie Klassen <[email protected]>

v0.0.0-1599160821

use testify instead of ginkgo

fixes concourse/concourse#6033

Signed-off-by: Jamie Klassen <[email protected]>
Co-authored-by: Zoe Tian <[email protected]>

v0.0.0-1599061703

use cobra instead of go-flags

fixes concourse/concourse#6032

Signed-off-by: Jamie Klassen <[email protected]>
Co-authored-by: Zoe Tian <[email protected]>

v0.0.0-1597782445

Merge branch 'error-handling'

Co-authored-by: Jamie Klassen <[email protected]>

v0.0.0-1597699079

remove unecessary import

forgot to goimports after the big refactor

Signed-off-by: Jamie Klassen <[email protected]>

v0.0.0-1597347641

go module cleanup

* rename module to concourse/ft
* go mod tidy

Signed-off-by: Jamie Klassen <[email protected]>

v0.0.0-1597347308

clean up k8s worker

* no more unnecessary logging
* default to LAN worker, allow k8s worker override
* turns out we don't need to do anything with the error stream besides open it
* pull the determining of k8s-related defaults out of `main.go`

* if we can be a bit more careful with our tests, we should actually be able
  to remove the K8sConnection type and replace it with a rest.Config, where
  getting the URL path to a portforward action should be a matter of calling
  rest.RESTClientFor and then using the fluent APIs, as is currently hidden in
  the implementation of systemK8sConnection.

Signed-off-by: Jamie Klassen <[email protected]>

v0.0.0-1596644264

publish continuously

we have no backwards compatibility requirements yet, so never wait to ship!

Signed-off-by: Jamie Klassen <[email protected]>
Co-authored-by: Taylor Silva <[email protected]>