-
Notifications
You must be signed in to change notification settings - Fork 81
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
feat: allow YAML output #628
Conversation
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## main #628 +/- ##
==========================================
- Coverage 31.61% 31.54% -0.08%
==========================================
Files 171 171
Lines 7857 7872 +15
==========================================
- Hits 2484 2483 -1
- Misses 5090 5106 +16
Partials 283 283 ☔ View full report in Codecov by Sentry. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you also add to the the describe base command? It currently allows JSON but not YAML output.
🤖 I have created a release *beep* *boop* --- ## [1.41.0](v1.40.0...v1.41.0) (2023-12-13) ### Features * allow YAML output ([#628](#628)) ([87552d2](87552d2)) * **server:** allow to filter list by server status ([#629](#629)) ([1cb51f2](1cb51f2)), closes [#623](#623) ### Bug Fixes * make JSON/YAML outputs consistent ([#622](#622)) ([43944b8](43944b8)) * **server:** properly format request-console JSON output ([#626](#626)) ([40641b6](40641b6)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please).
This PR adds support for the
-o=yaml
flag wherever-o=json
is possible. It uses https://github.com/goccy/go-yaml, which uses the already existing JSON tags on schema structs, so they don't need to be modified.