Catch¶

A catch statement is also a sequence of operations or collectors.

Operations and collectors contained in a catch statement will be executed only if the step failed when executing the operations in the step's try statement.

Tip

All operations and collectors of a catch statement will be executed regardless of the success or failure of each of them.

More general catch blocks¶

Under certain circumstances, it can be useful to configure catch blocks at a higher level than the step grain. At the test or configuration level.

This allows for declaring common catch statements we want to execute when an error occurs. Those catch blocks are combined to produce the final catch block in the following order:

catch statements from the configuration level are executed first (if any)
catch statements from the test level are executed next (if any)
catch statements from the step level are executed last (if any)

Operations¶

A catch statement supports only the following operations:

Collectors¶

A catch statement supports all collectors:

Examples¶

step level catch block

apiVersion: chainsaw.kyverno.io/v1alpha1
kind: Test
metadata:
  name: example
spec:
  steps:
  - try: []
    catch:
    - command:
        # ...
    - script:
        # ...
    - delete:
        # ...
    - events:
        # ...
    - podLogs:
        # ...
    - describe:
        # ...
    - get:
        # ...
    - sleep:
        # ...
    - wait:
        # ...
    finally: []

test level catch block

apiVersion: chainsaw.kyverno.io/v1alpha1
kind: Test
metadata:
  name: example
spec:
  catch:
  - command:
      # ...
  - script:
      # ...
  - delete:
      # ...
  - events:
      # ...
  - podLogs:
      # ...
  - describe:
      # ...
  - get:
      # ...
  - sleep:
      # ...
  - wait:
      # ...
  steps:
  - try: []
    finally: []