We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
There was an error while loading. Please reload this page.
skupper site status
-o
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
Describe the bug
Exactly what it says on the tin
How To Reproduce
$ skupper site status -o json NAME STATUS MESSAGE asdf Ready OK $ skupper site status -o yaml NAME STATUS MESSAGE asdf Ready OK
Expected behavior
An YAML or JSON output
Environment details
Additional context
Not applicable
The text was updated successfully, but these errors were encountered:
Additionally, on site status:
site status
$ skupper site status NAME STATUS MESSAGE west Ready OK $ oc get sites.skupper.io NAME STATUS SITES IN NETWORK MESSAGE west Ready 2 OK
It does not relay the SITES IN NETWORK column — is that intentional?
SITES IN NETWORK
Sorry, something went wrong.
@hash-d "sites in network" is not specified in refdog, so that is why it is not displayed in the cli output. https://skupperproject.github.io/refdog/commands/site/status.html
But it could be added if @ssorj agrees
@noe The site command does appear to be missing the -o flag processing. I can add it.
lynnemorrison
Successfully merging a pull request may close this issue.
Describe the bug
Exactly what it says on the tin
How To Reproduce
Expected behavior
An YAML or JSON output
Environment details
Additional context
Not applicable
The text was updated successfully, but these errors were encountered: