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
Please describe the scenario where the new feature would be useful
In situations where we programmatically use the pro client, it would be much easier if there was a dedicated CLI command or options that would simply return a boolean response to whether the machine is attached or not. Today we have to do this by parsing the output of pro status or pro api u.pro.status.is_attached.v1 which may introduce an additional dependency (like jq) and forces the users/programs to know exactly which key provides the value of
Describe the solution you'd like
Ideally a new command like pro is-attached or maybe an option pro status --is-attached.
Current behavior
Currently need to pro api u.pro.status.is_attached.v1 | jq .is_attached.
The text was updated successfully, but these errors were encountered:
No restrictions here, at least for now (I could speculate some chiselled/distroless cases where utilities might be limited).
This is a suggestion for improvement, as it feels like other programs using the Pro client should rely on it to just provide a yes/no answer on this "status" question (e.g. something like pebble health)
Please describe the scenario where the new feature would be useful
In situations where we programmatically use the
pro
client, it would be much easier if there was a dedicated CLI command or options that would simply return a boolean response to whether the machine is attached or not. Today we have to do this by parsing the output ofpro status
orpro api u.pro.status.is_attached.v1
which may introduce an additional dependency (likejq
) and forces the users/programs to know exactly which key provides the value ofDescribe the solution you'd like
Ideally a new command like
pro is-attached
or maybe an optionpro status --is-attached
.Current behavior
Currently need to
pro api u.pro.status.is_attached.v1 | jq .is_attached
.The text was updated successfully, but these errors were encountered: