Configuration file¶

Chainsaw is described as a Stronger tool for e2e testing.

With its versatile configuration options, you can customize the testing process to fit your needs.

Chainsaw prioritizes its configuration in the following order:

1. User-specified configuration

   If you explicitly provide a configuration file using a command-line flag

2. Default configuration file

   If no configuration is specified, Chainsaw will look for a default file named .chainsaw.yaml in the current working directory

3. Internal default configuration

   In the absence of both the above, Chainsaw will use a default configuration file embedded in the Chainsaw binary

Example¶

apiVersion: chainsaw.kyverno.io/v1alpha1
kind: Configuration
metadata:
  name: custom-config
spec:
  timeouts:
    apply: 45s
    assert: 20s
    cleanup: 45s
    delete: 25s
    error: 10s
    exec: 45s
  skipDelete: false
  failFast: true
  parallel: 4
  # ...

How to specify a configuration¶

To use a custom configuration file:

$ chainsaw test --config path/to/your/config.yaml

Default configuration¶

The default configuration below is used by Chainsaw when no configuration file was provided and the default file .chainsaw.yaml does not exist.

apiVersion: chainsaw.kyverno.io/v1alpha1
kind: Configuration
metadata:
  name: default
spec: {}

Reference documentation¶

See Configuration API reference for more details.