Skip to content

Exceptions

Everything CATS raises deliberately is a CatsError; the three caller-facing classes and the rule are in the compatibility contract.

Exceptions raised by CATS.

Everything CATS raises deliberately is a CatsError, so except CatsError catches all of it. Callers see three kinds for their own mistakes and their environment:

  • CatsUsageError for an argument CATS cannot act on (also a ValueError).
  • CatsConfigError for their configuration: an invalid or missing cats.yaml (pydantic's report is embedded in the message), an unknown account name, a feature the config does not enable, a Region that is set nowhere.
  • CatsInfrastructureError for AWS infrastructure that is missing, from another release, or unreachable, including the environment's own credential and endpoint failures at the session boundary.

The one exception: CatsTestPack is a pydantic model, so constructing one with bad fields raises pydantic's ValidationError, as its docstring states.

CatsConfigError

Bases: CatsError

The configuration is invalid, missing, or does not enable this action: an invalid cats.yaml, an unknown account, an unset Region.

CatsError

Bases: Exception

Base for all CATS exceptions.

CatsInfrastructureError

Bases: CatsError

CATS infrastructure is missing, misconfigured or unreachable. Deploy or redeploy, or fix the environment's AWS access.

CatsLambdaInvocationError

Bases: CatsError

Lambda invocation returned an error instead of a result.

CatsSSMError

Bases: CatsError

SSM command execution failed.

CatsUsageError

Bases: CatsError, ValueError

The caller passed an argument CATS cannot act on: a bad port, a URL where a hostname was expected, an undeclared @cats keyword.

CatsVersionMismatchError

Bases: CatsInfrastructureError

Deployed stack was created by a different CATS release; destroy and deploy.