Open sadsfae opened 3 months ago
FWIW there's two additional ways to get this information, though I think the old functionality should be restored.
via --ls-schedule
quads --ls-schedule --host e33-h15-000-r650.rdu2.example.com | grep "Current cloud" | sed 's/Current cloud://'
cloud27
via the API
curl -s -X GET "https://quads2.example.com/api/v3/hosts?name=e33-h15-000-r650.rdu2.example.com" | jq | grep -C5 "\"cloud\":" | grep "name" | sed 's/\"name\"\://'
"cloud27"
So this has an added effect that if you typo something with --host*
in it (like forgetting a sub-command for `--add-schedule) it return this too.
[root@quads2-stage ~]# quads --host-list /tmp/3753 --schedule-start "2024-09-12 12:00" --schedule-end "2024-09-13 12:00" --schedule-cloud cloud04
--add-schedule
command and the argparse fell back and matched instead --host
cloud01:
in QUADS 1.1.x
quads-cli --host $HOST
returned the current cloud something was in:In QUADS 2.0 it returns this, but also a gigantic return of all cloud and host breakdown.