Angus Lees

oh, and the first of the two commits rewrites `show_test.go` as an integration test. Fixes #99

Reopening, since some of the details here are diff-specific (namespace in local objects) and separate to #103.

Fwiw: #16 is almost a duplicate, except the motivation is the `show` subcommand. Re above: I think picking a jsonnet (json) subtree would be super useful, particularly for debugging via...

I think this was fixed in #178, since that change uses "dependency" order and then falls back to alphabetical order (alpha sort on namespace/name/kind), which should be stable for any...

This just hurt bitnami-labs/sealed-secrets#99 #178 never fixed this for `sort` only other subcommands. The `sort` order is/was fixed to "jsonnet result order" which should be stable, but not easily predictable....

@primeroz hrm, I thought I had improved this. Which version are you using?

Urgh, thanks for reporting. Running in-cluster was definitely _meant_ to be a supported use case. There were long-running client-go bugs re running in-cluster but doing operations against another namespace -...

It's not pretty, but @sebgoa points out that this works in-cluster as a workaround: ``` token=$(cat /var/run/secrets/kubernetes.io/serviceaccount/token) kubecfg --certificate-authority=/var/run/secrets/kubernetes.io/serviceaccount/ca.crt --token $token --server https://kubernetes:443 update ... ``` (assuming RBAC allows the...

Yes, the diff output could do with a lot more cleanup (a real simple example would be removing the status fields, etc that we *know* aren't going to appear in...

I'm happy to switch to bazel - what I _don't_ want to do is to maintain two build systems in parallel (like k8s). And of course the downside of switching...