-
Notifications
You must be signed in to change notification settings - Fork 302
Allow user to define fields returned in fleetctl list-units and list-machines #337
Conversation
14.8% -> 18.8% coverage. yay. I'm not sold on the name of the option, so very open to suggestions. |
Also this doesn't implement |
Failing tests:
|
} | ||
return d | ||
}, | ||
"machine": func(j *job.Job, full bool) string { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Once this lands, it would be a good idea to provide "public-ip" and "machine-id" fields.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nod. #179 shows how easy this makes it to add new fields ;-)
Fixed silly test breakage. |
Renamed to |
lgtm |
Cool beans. |
Allow user to define fields returned in fleetctl list-units
👍 This helps us parse the job's state, such as what we attempt to accomplish here. Being able to define the fields returned from Nice work guys :) |
e.g.