Why volumes do not have IDs?

[project0]

I am currently working with the bindings and stumbled across some inconsistency of resource definitions.

I wonder why volumes do not have any ID?
Is name attribute enough to distinguish resources? But why do have all other resources IDs along to the name?

[mheon]

This is mainly a Docker compat thing - Docker volumes just use a name as an identifier, without an ID, so we haven’t felt the need to add one to our volumes. Why the original decision to have them be the only major type without an ID was made, I have no idea.

…

On Sun, Apr 17, 2022 at 08:46 Richard Hillmann ***@***.***> wrote: I am currently working with the bindings and stumbled across some inconsistency of resource definitions. I wonder why volumes do not have any ID? Is name attribute enough to distinguish resources? But why do have all other resources IDs along to the name? — Reply to this email directly, view it on GitHub <#13903>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AB3AOCG5K7RPSFQ7OSWGK6LVFQB3FANCNFSM5TT2UFMA> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>