lasdf1234 opened a new issue, #14226: URL: https://github.com/apache/gravitino/issues/14226
### Version main (2.0.0-SNAPSHOT) ### Describe what's wrong When a configured secret provider cannot be reached, `GET .../secrets` fails as an internal server error (HTTP 500). Callers cannot tell a temporary dependency outage from a Gravitino bug. `SecretExceptionHandler` already maps domain failures such as `IllegalArgumentException` / `NotFoundException`, but `ConnectionFailedException` falls through to the generic handler and becomes 500. Catalog handlers already treat `ConnectionFailedException` as a dependency failure (HTTP 502). ### How to reproduce 1. Configure a secret provider that talks to an external store. 2. Stop or block that store so provider calls throw `ConnectionFailedException`. 3. Call `getSecrets` on an object that resolves secrets through that provider. 4. Observe HTTP 500 instead of a dependency-style status. ### Additional context Pass criteria: `getSecrets` returns **HTTP 503** with a connection-failed error payload when the secret provider is unavailable. The response message must not expose internal backend request paths. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
