Support for --dry-run=client about kubectl-aliases HOT 5 CLOSED

The "write commands" are relatively low % of the list. Namely only "delete" commands can benefit from this, and I am not sure if one would actually benefit that much from dry-run=client deletion. :)

Please explain which one of the commands would benefit from this.

from kubectl-aliases.

The CKAD exam is also and exercise in creating objects quickly as you will not pass it if you type out all the yaml.

So we are drilled with using imperative commands to quickly constuct resource.

Some examples
k create deploy x --image x --dry-run=client -o yaml > x.yaml

Now we are free to first edit the file for properties which aren't available at the command line e.g. adjust the container name, specify a service account etc

k run x --image x --expose --port 80 --dry-run=client -o yaml > x.yaml

Bam, now we have a pod and a service at the same time and ready to be edited/tweaked before applying

With some kubectl-aliases both scenario's would translate to

kcdepdryoyaml x --image x > x.yaml

krdryoyaml x --image x --expose --port 80 > x.yaml

And now, when I'm writing this out, I see that the command 'create' and 'run' are not supported at the moment.
Were these intentionally left out?

Maybe you want to keep a more narrow focus with this project?

from kubectl-aliases.

I was under the impression that this project reflected over the cli command/options programmatically, generated the abbreviation, reported on duplicates that needed disambiguation, and then either blocklisted certain combinations or translated commands/options to aliases that removes the ambiguity as was done with the following instance
d=describe
d=>rm=delete

from kubectl-aliases.

You're right but this project only has delete command's aliases where dry run can apply. And is it that much valuable there?

We don't offer programmatically generated aliases for create/apply really.

from kubectl-aliases.

Dry run for the delete command doesn't add value IMO.

If it is not the desire to have the create/run/expose commands in scope I suggest we close this issue. If you think this has a place I can start contributing.

from kubectl-aliases.