wish / ctl Goto Github PK

For example, if default_columns is 'env', ctl get pods --env=prod should exist and be equivalent to ctl get pods -l env=prod

ctl configuration should be stored in $XDG_CONFIG_DIR/ctl. If XDG_CONFIG_DIR is not set, default to ~/.config. $XDG_CONFIG_DIR/ctl/config.yml

needs to support other objects other than pod, so move the object (pod) under get

Should pretty print the yaml

i.e., ctl get pods foo should act like the user only wants pods that start with foo, as if ^foo were entered.

defaults to localhost which prevents other hosts from hitting it.. great for testing, not so great for deploying.

Hi there.

This might be an unusual "issue" beeing reported.

There has been a security incident in codecov.io with the bash-uploader script (see [1] for details) which potentially exposed secrets to 3rd parties.

It seems you are using the referenced bash uploader in your .travis.yml file. I wanted to draw your attention to this incident in case you missed it.

It would be great if you could verify that no code has been altered and check the impact of this security incident on your repository.

Regards,
Robert

[1] https://about.codecov.io/security-update/

ctl describe foo no longer works, neither does ctl describe pod foo. Add test so we don't break going forward.

Unclear which resources can be queried with get/describe. Without any resource ctl get just says 'expects another argument' and ctl get --help doesn't list the resources either.

If we treated foo like a regular expression if would make filtering by podname easier. Right now ctl doesn't seem to be doing anything with 'foo' though it accepts it.

If a job spawns resources such as pods, calling ctl delete job should delete the child resources just like kubectl delete job

ctl should be able to support get/describe CRDs like kcd.
E.g.
ctl get kcd -n kube-deploy
ctl describe kcd -n kube-deploy

to access custom resources.

1. ConfigMaps

Need to package this up for easier consumption. Let's try goreleaser. And since ctl is tightly linked to k8s apis, let's use the k8s version numbers to indicate compatiblity. Let's give k8s the first 2 digits, we can take the following 2. So, 1.10 + .0.1 for the first release, i.e., 1.10.0.1

Inform the user prior to running command that the first container in the pod has been chosen, the name of that container, and the flag to change the container and the available container names in the pod.

should work with -f as well

might need to limit this in the case when it matches a lot of pods? like more than 100?

Currently, ctl run has to match exactly by name. Users should be able to retrieve an available list of run commands available. However, this can be complex if commands vary by cluster.

If default_columns specified in one of the cluster configs specify show the key:value label pair as output in get

Can assume default_columns is <= 4 to make the ui a little bit easier.