Failing unsupported commands with proper message. Fixes #48.

[prashima]

Commands followed by error message

With feature flag set:

kops create ig --name=v1c1.skydns.local --role=Node --subnet=vmw-zone nodes2 Command create ig is not yet supported for vsphere cloud provider.

kops delete instancegroup --name=v1c1.skydns.local nodes.v1c1.skydns.local Command delete ig is not yet supported for vsphere cloud provider.

kops delete -f ~/Downloads/inbox/kops/s3-state/cluster3/vSphere/kops.nodeig.yaml --name=v1c1.skydns.local --yes Command delete ig is not yet supported for vsphere cloud provider.

kops edit cluster --name=v1c1.skydns.local Command edit cluster is not yet supported for vsphere cloud provider.

kops edit ig --name=v1c1.skydns.local nodes Command edit ig is not yet supported for vsphere cloud provider.

kops replace -f ~/Downloads/inbox/kops/s3-state/cluster3/vSphere/config.yaml --name=v1c1.skydns.local error: Command replace -f is not yet supported for vsphere cloud provider.

kops rolling-update cluster --name=v1c1.skydns.local Command rolling-update cluster is not yet supported for vsphere cloud provider.

kops toolbox convert-imported --name=v1c1.skydns.local Command toolbox convert-imported is not yet supported for vsphere cloud provider.

kops update cluster --name=v1c1.skydns.local Command update cluster is not yet supported for vsphere cloud provider.

kops upgrade cluster --name=v1c1.skydns.local Command upgrade cluster is not yet supported for vsphere cloud provider.

Without feature flag:

kops edit ig --name=v1c1.skydns.local nodes Feature flag VSphereCloudProvider is not set. Cloud vSphere will not be supported.

This fix does not include following commands because no cloud provider is getting queried for these commands. So it's not possible to decide if a command is meant for vSphere. Additional parameters will have to be added for this.

• replace -f for instance groups
• edit federation
• update federation
• import cluster