Raised when a key provider returned an opaque AshVault.Key handle to a cipher that
can only work on raw key bytes.
This is a configuration fault, not a transport failure and emphatically not tampering: the pairing of provider and cipher is wrong and will be wrong on every retry. The alternative — silently fetching the bytes out of the handle and carrying on — would put the key back on the BEAM heap, which is the exact thing the handle exists to prevent, so AshVault refuses instead.
Summary
Functions
Create an Elixir.AshVault.Errors.OpaqueKeyUnsupported without raising it.
Functions
@spec exception(opts :: Keyword.t()) :: %AshVault.Errors.OpaqueKeyUnsupported{ __exception__: true, bread_crumbs: term(), cipher: term(), class: term(), field: term(), operation: term(), path: term(), provider: term(), resource: term(), splode: term(), stacktrace: term(), vars: term() }
Create an Elixir.AshVault.Errors.OpaqueKeyUnsupported without raising it.
Keys
- :cipher
- :provider
- :resource
- :field
- :operation