We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
in QUADS 1.1.x quads-cli --host $HOST returned the current cloud something was in:
quads-cli --host $HOST
(root@quads11) - (12:41) - (~) # quads --host d16-h01-000-r650.rdu2.example.com cloud37
In QUADS 2.0 it returns this, but also a gigantic return of all cloud and host breakdown.
# quads --host d16-h01-000-r650.rdu2.example.com | head -n 10 cloud01: - d17-h27-000-r650.rdu2.example.com - d17-h28-000-r650.rdu2.example.com - d17-h29-000-r650.rdu2.example.com -- SNIP --
The text was updated successfully, but these errors were encountered:
FWIW there's two additional ways to get this information, though I think the old functionality should be restored.
--ls-schedule
quads --ls-schedule --host e33-h15-000-r650.rdu2.example.com | grep "Current cloud" | sed 's/Current cloud://' cloud27
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"
Sorry, something went wrong.
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.
--host*
[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
--host
cloud01:
No branches or pull requests
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.
The text was updated successfully, but these errors were encountered: