Enum SecretError 

#[non_exhaustive]
pub enum SecretError {
    NotFound,
    Backend {
        backend: &'static str,
        source: Box<dyn Error + Send + Sync>,
    },
    InvalidUri(String),
    DecodeFailed(String),
    Unavailable {
        backend: &'static str,
        source: Box<dyn Error + Send + Sync>,
    },
    DataLost {
        backend: &'static str,
        message: String,
    },
    AlgorithmMismatch {
        expected: &'static str,
        actual: String,
    },
}

Errors returned by secret store operations.

Variants (Non-exhaustive)

Non-exhaustive enums could have additional variants added in future. Therefore, when matching against variants of non-exhaustive enums, an extra wildcard arm must be added to account for any future variants.

NotFound

Backend returned no secret for this name/path.

Backend

Backend encountered a permanent error — retrying will not help.

Examples: authentication failure, permission denied, malformed request, the named secret was deleted. Callers should surface this to the operator or abort rather than retrying automatically.

For transient failures where a retry may succeed (network timeouts, 5xx responses, temporary outages), use Unavailable.

Fields

backend: &'static str

source: Box<dyn Error + Send + Sync>

InvalidUri(String)

URI was syntactically invalid or named an unknown/disabled backend.

DecodeFailed(String)

Secret was present but could not be decoded as expected.

Unavailable

Backend is temporarily unavailable — retrying may succeed.

Examples: network timeout, DNS failure, connection refused, HTTP 5xx from a remote secrets service. Callers should implement retry with back-off rather than failing immediately.

For permanent errors that will not resolve on retry, use Backend.

Fields

backend: &'static str

source: Box<dyn Error + Send + Sync>

DataLost

Data was irrecoverably lost during a write operation.

The backend deleted existing data but failed to write the replacement. The original data is permanently gone. Callers should log an alert and may need to recreate the lost entry.

message describes what was lost (e.g. an object ID or key name).

Fields

backend: &'static str

message: String

AlgorithmMismatch

The backend’s key algorithm does not match what the caller expected.

Returned by adapter layers (e.g. secretx-signature) when a SigningBackend is wrapped in a typed signer for a different algorithm.

Fields

expected: &'static str

actual: String

Trait Implementations

impl Debug for SecretError

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl Display for SecretError

fn fmt(&self, __formatter: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl Error for SecretError

fn source(&self) -> Option<&(dyn Error + 'static)>

Returns the lower-level source of this error, if any.

fn description(&self) -> &str

👎Deprecated since 1.42.0:

use the Display impl or to_string()

fn cause(&self) -> Option<&dyn Error>

👎Deprecated since 1.33.0:

replaced by Error::source, which can support downcasting

fn provide<'a>(&'a self, request: &mut Request<'a>)

🔬This is a nightly-only experimental API. (error_generic_member_access)

Provides type-based access to context intended for error reports.