-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Clone] Error Standardization: Secrets API #7690
Labels
stale
Issues and PRs without response
Comments
/assign |
7 tasks
This issue has been automatically marked as stale because it has not had activity in the last 60 days. It will be closed in the next 7 days unless it is tagged (pinned, good first issue, help wanted or triaged/resolved) or other activity occurs. Thank you for your contributions. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Richer errors in Dapr for the Secrets API.
Original #7484
Scope of work
Choose 5-10 errors in the Secrets 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
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:
Reference PRs
Existing error standardization for:
#7257
#7322
The text was updated successfully, but these errors were encountered: