Inconsistent resource objects when output format is json

[MarkusFreitag]

When setting the output format to json, the resource object is rendered differently between the corresponding list and describe command.

The following json output is just an example, this behaviour is not limited to the iso resource.

# list all isos
[{"id":1,"name":"dvd_a.iso","description":"DVD A","type":"","deprecated":"0001-01-01T00:00:00Z"},{"id":2,"name":"","description":"cd_b.iso","type":"","deprecated":"0001-01-01T00:00:00Z"}]

# describe iso 1
{"deprecated":null,"description":"DVD A","id":1,"name":"dvd_a.iso","type":"public"}

# describe iso 2
{"deprecated":null,"description":"cd_b.iso","id":2,"name":null,"type":"private"}

After digging a bit into this, I noticed that a ListCmd has a JSONSchema attribute which converts the resource into a hcloud-go api schema object before decoding it into a JSON string. In contrast the DescribeCmd just decodes the resource object directly.

[github-actions]

This issue has been marked as stale because it has not had recent activity. The bot will close the issue if no further action occurs.

[github-actions]

This issue has been marked as stale because it has not had recent activity. The bot will close the issue if no further action occurs.