The only information we currently get from the API response is the ID (and, weirdly, 'delete_on_termination'). It'd be neat to get more (particularly the volume name, size and device name) but as long as it's not present in the API response the ID alone is fine.
If it requires another database query that's considered too expensive/complicated we can treat volume attachments as a special case that we need to be aware of, but the aim of these tickets is to identify those fields and preferably reduce the number we have to deal with separately.
The only information we currently get from the API response is the ID (and, weirdly, 'delete_ on_termination' ). It'd be neat to get more (particularly the volume name, size and device name) but as long as it's not present in the API response the ID alone is fine.
If it requires another database query that's considered too expensive/ complicated we can treat volume attachments as a special case that we need to be aware of, but the aim of these tickets is to identify those fields and preferably reduce the number we have to deal with separately.