Error Standardization: Configuration API

[cicoyle]

Richer errors in Dapr for the Configuration API.

Note: Please clone this issue and assign the clone of this issue to yourself if you would like to contribute to the error standardization efforts.

Scope of work

• Choose 5-10 errors in the Configuration API to enrich. Ideally, cover as many errors as possible from the API.
• Follow the steps outlined in this README for each error being updated

Definition of done

• Update 5-10 errors in the Configuration API
• Update the unit tests, if necessary
• Write integration tests to cover each updated errors

Keep in mind

Unless a major version is being released and there is a solid reason for introducing backwards incompatibility, we can't change the API, meaning the HTTP and gRPC status codes, and the error codes must stay the same. An exception to this is the gRPC StatusCode.UNKNOWN which should be converted to a specific status.

See the kit errors pkg README for another usage example. For each error being updated, you can use the following helper functions to add error details, see the kit errors pkg for more details:

• WithHelpLink()
• WithHelp()
• WithErrorInfo() - Required
• WithFieldViolation()
• WithDetails()

Reference PRs

Existing error standardization for:

• State API
• PubSub API

[stackanthony]

Hi @cicoyle, does this issue still need to be worked on? I haven't contributed to the project yet, but looking forward to working on this one, if possible.

[cicoyle]

Hi @cicoyle, does this issue still need to be worked on? I haven't contributed to the project yet, but looking forward to working on this one, if possible.

Yes @stackanthony, this is available to be worked on. I'm happy to hear you are interested in contributing to Dapr. Please clone this issue and assign yourself to it.

Please lmk if you need any assistance along the way 🙂

[stackanthony]

Forsure, will do. I'll need some time to get acclimated to the codebase. Will let you know if I have any questions.

P.S. - I worked at HashiCorp too, awesome to see someone from there contributing to the project @cicoyle

[stackanthony]

When you say clone this issue, how exactly should I do this? I've never done something like cloning an issue, only a repo lol. Can't find anything online about it either, maybe I misunderstood. @cicoyle

[cicoyle]

@stackanthony - clone as in, create a new issue, copy/paste the content, then assign your name to it :) Ah cool - I was at HashiCorp for a while, and am very happy to be at Diagrid now

[stackanthony]

Cool, just did it. Referenced in #7785 @cicoyle