Status Update
No update yet.
Comments
wb...@google.com
Hello and thanks for sharing this idea with us.
I'm passing this to the product team for further analysis and they will come back with the information if this feature can be implemented. There's no ETA for this however.
If you want to add anything - describe requested feature better or just ask a question please feel free.
Someone will get back to you if there's any change or we need some information from you.
cb...@ztb.icb.commerzbank.com
We also require the same functionality. When creating keyrings there are occasionally errors, new keyrings are then created but the incorrectly created ones can unfortunately no longer be deleted - why not use something like a UUID instead of the names, so there would be no collisions and the customers can use any name they want?
nu...@jdsplatform.com
it would be great if customer have the capability to delete keyrings. Since there's a chance human error, changing naming convention, etc. If the "old" keyrings still there, shown in the console, it's like leaving the orphan infrastructure and can make new engineer joined to the team get confused.
rh...@ebay.com
This would be useful, it doesn't make sense to keep keyrings around if they have had no versions before. One was accidently created in the wrong region, never used and cannot be deleted, very frustrating.
[Deleted User] <[Deleted User]>
After exactly one year, we are still looking forward to this feature. ;)
Can you share any news?
Can you share any news?
gr...@google.com
I'm marking this issue as a duplicate of
I believe this is not currently on our roadmap, but I'll double check with the rest of the team and share an update
Description
What you would like to accomplish: To be able to delete keyrings.
How this might work: Currently, there is no ability to delete a keyring to prevent name collisions