It supports text and json output formats. But there's a difference due to the SO backend API's behavior: it provides CreationTime and TerminationTime as Unix timestamps.
text: CreationTime and TerminationTime are converted to RFC3339 format. More human-readable.
json: These timestamps are kept as Unix timestamps, as returned by the SO backend API.
The discrepancy between the formats is due to the SO backend API exclusively providing Unix timestamps. I'm open to suggestions for improving these output formats.
This description explains the reasoning behind the different timestamp formats in text and json outputs and invites feedback on this implementation.
Types of changes
[ ] Bugfix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation Update (if none of the other choices apply)
Checklist
[ ] Lint and unit tests pass locally with my changes
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have added necessary documentation (if appropriate)
[ ] I have updated the json schema (if appropriate)
Proposed changes
Add cli to list containers:
JSON output
It supports
text
andjson
output formats. But there's a difference due to the SO backend API's behavior: it providesCreationTime
andTerminationTime
as Unix timestamps.text
:CreationTime
andTerminationTime
are converted to RFC3339 format. More human-readable.json
: These timestamps are kept as Unix timestamps, as returned by the SO backend API.The discrepancy between the formats is due to the SO backend API exclusively providing Unix timestamps. I'm open to suggestions for improving these output formats.
This description explains the reasoning behind the different timestamp formats in
text
andjson
outputs and invites feedback on this implementation.Types of changes
Checklist
Further comments