You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With more Rest based API integrations added to Prysm we need more flexibility with our API middleware/gRPC gateway setup. Currently, our API Middleware/ gRPC gateway setup doesn't allow us to return custom codes for successes (so only 200 ok)
these are the current mappings
Ideally, we would like a way to override this for more custom codes such as 202 on our API returns.
🚀 Feature Request
Description
With more Rest based API integrations added to Prysm we need more flexibility with our API middleware/gRPC gateway setup. Currently, our API Middleware/ gRPC gateway setup doesn't allow us to return custom codes for successes (so only 200 ok)
these are the current mappings
Ideally, we would like a way to override this for more custom codes such as 202 on our API returns.
some examples where this is used.
Describe the solution you'd like
we should provide a way to customize a new gRPC option for custom returns
https://grpc-ecosystem.github.io/grpc-gateway/docs/mapping/customizing_your_gateway/#controlling-http-response-status-codes
The text was updated successfully, but these errors were encountered: