errors
etl_craft.core.errors ¶
The error hierarchy, and the exit status the command line returns for each error.
Every error etl-craft raises on purpose is an EtlCraftError, and every error class has its
own exit status, so a scheduler or script can tell exactly what went wrong from the status
alone. ExitCode lists them all.
ExitCode ¶
Bases: IntEnum
The exit status of an etl-craft command.
EtlCraftError ¶
Bases: Exception
Base class of every error etl-craft raises; each subclass has its own exit status.
ConfigurationError ¶
Bases: EtlCraftError
craft-connector.yml, a secret or a connection target cannot be used.
Covers a missing or invalid file, an unset secret variable, a JDBC URL or auth mode with no matching dialect, and an Engine DB that cannot be reached.
UsageError ¶
MetadataError ¶
GraphError ¶
RunStateError ¶
RunRefusedError ¶
Bases: EtlCraftError
The run is not allowed in the configured mode, for example --force in remote mode.
ConnectionTestError ¶
EngineDbError ¶
MigrationError ¶
LockTimeoutError ¶
HandlerError ¶
CloningError ¶
Bases: EtlCraftError
Copying an Engine DB table into the warehouse failed; the message names the table.
RemoteUnsupportedError ¶
Bases: EtlCraftError
A pipeline has rules a remote orchestrator does not support; the message names each.
InjectedFaultError ¶
StaleTransitionError ¶
Bases: EtlCraftError
A lifecycle write lost its status or owner guard; refresh the row before retrying.