-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
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
cmd/status: endpoint implementation #42
Conversation
My2cents Could be great to convert it into something we could use in scripts with json output. |
Generally speaking, I think it would be nice to have formatting (which in the end do not format anything received 😄 ) flags. |
What do you mean ? We already have the $ ./cy status -o json | jq
Warning: CLI version v1.0.48 does not match the API version. You should consider to download CLI version v1.0.47
[
{
"canonical": "database",
"category": "internal",
"message": "no issue reported while connecting to the database service",
"status": "Success"
},
{
"canonical": "pipeline",
"category": "internal",
"message": "no issue reported while connecting to the pipeline service",
"status": "Success"
},
...
$ ./cy status -o yaml
Warning: CLI version v1.0.48 does not match the API version. You should consider to download CLI version v1.0.47
- canonical: database
category: internal
message: no issue reported while connecting to the database service
status: Success
... |
Then I don't get @gaelL comment ^^ |
Initial implementation of the
/status
endpoint. With colors on the table displayCloses: #27