You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Obviously the "describe cluster" output doesn't have a .hardware.cpu_cores and the "machine ls" output has no .Status.lastOperation.progress. Also the template I used here didn't mention Cluster: or Machines:, these headers had been printed directly and independently from the output type as it seems.
So, it would be nice to omit the "describe cluster" output with an option so that only the machine status list is being displayed. Or - maybe better - make this the default as the command name "cluster machine ls" suggests it anyway, and add an option to include the "describe cluster" output.
The text was updated successfully, but these errors were encountered:
The command
cloudctl machine ls $cluster
shows 2 outputs: first the one ofcloudctl cluster describe $cluster
and then the actual machine status.This is all fine and dandy unless you want to post-process the output using template vars. E.g.:
Obviously the "describe cluster" output doesn't have a
.hardware.cpu_cores
and the "machine ls" output has no.Status.lastOperation.progress
. Also the template I used here didn't mentionCluster:
orMachines:
, these headers had been printed directly and independently from the output type as it seems.So, it would be nice to omit the "describe cluster" output with an option so that only the machine status list is being displayed. Or - maybe better - make this the default as the command name "cluster machine ls" suggests it anyway, and add an option to include the "describe cluster" output.
The text was updated successfully, but these errors were encountered: