Deprecated CLI Arguments Used in Documentation

[danchirillo]

The command line arguments at Setting up the API key to enable access to the infrastructure portfolio are no longer valid for the current release (as of today) of ibmcloud CLI (version 0.15.1+d1a593d-2019-04-11T08:00:31+00:00).

[Rachael-Graham]

@danchirillo Which arguments?

[danchirillo]

Hi @Rachael-Graham

I had an issue with the ks argument. Just a bit of history before I get into details. I don't know which version I was running prior to today, but at the command line today I was prompted to upgrade ibmcloud CLI:

I then ran into an aside with the ks argument. Here is the complaint. Note that ks is not in the list of valid commands:

In the same shell, I later ran curl -sL https://ibm.biz/idt-installer | bash per the instructions for setting up a Kubernetes cluster:

Now, in the same shell, ks is a valid argument:

Might it be the case that installing the ibmcloud command CLI does not by default add the Kubernetes support?

[Rachael-Graham]

Yes, I think you have it right--When you install the ibmcloud CLI by itself, you have to then also manually install the ks plugin for it by running ibmcloud plugin install kubernetes-service. However, if you use that installer script, then the plugin is installed automatically.

BUT that being said, you're also correct in that updating your ibmcloud cli should definitely not uninstall your ks plugin. I'll investigate with the core ibmcloud CLI team.

[danchirillo]

That explains it, then. I had not installed the Kubernetes plugin prior to the upgrade, which makes this an operator error issue ;)

[Rachael-Graham]

Ohh okay makes sense! Closing this issue then. 🎉