spire-server: Better status codes from BatchCreateEntry API #5444
Labels
help wanted
Issues with this label are ready to start work but are in need of someone to do it
priority/backlog
Issue is approved and in the backlog
The BatchCreateEntry currently returns some status codes, InvalidArgument, InternalError (for most database issues), AlreadyExists. If I try to create an entry with some invalid parameters, e.g. entry id too long or empty list of selectors, I get back an InternalError status code. This makes it hard to differentiate between user errors (invalid entry) and database entries. I'd like to be able to differentiate between them to know if I need to retry creating a registration entry at a later time or know that it will never work.
The text was updated successfully, but these errors were encountered: