This is more like a feature request. Keypair resource is unique in a way that they are user specific resources while the rest is project specific. Nova API already allows for an admin to query the keypairs of a specific user [0]. If this is not enough then I suggest you to raise this change as a blueprint[1] (i.e. a new feature) and add a discussion item to the regular nova meeting agenda[2] or to the upcoming PTG.
This is more like a feature request. Keypair resource is unique in a way that they are user specific resources while the rest is project specific. Nova API already allows for an admin to query the keypairs of a specific user [0]. If this is not enough then I suggest you to raise this change as a blueprint[1] (i.e. a new feature) and add a discussion item to the regular nova meeting agenda[2] or to the upcoming PTG.
I marking this as whislist
[0] https:/ /docs.openstack .org/api- ref/compute/ ?expanded= list-keypairs- detail# list-keypairs /docs.openstack .org/nova/ latest/ contributor/ process. html /wiki.openstack .org/wiki/ Meetings/ Nova#Agenda_ for_next_ meeting
[1] https:/
[2] https:/