Configuration file reference
This document describes the configuration options provided by the user in YAML format.
Type: string
Description: The scanner API address of the TruffleHog server to connect to. This is given to you in the configuration file that you downloaded from your dashboard. Do not change it.
YAML Example:
Type: string
Description: The authentication token to use when connecting to the TruffleHog scanner. This is given to you in the configuration file that you downloaded from your dashboard. Do not change it.
YAML Example:
Type: string
Description: Specifies the scanner group to use within TruffleHog. This is given to you in the configuration file that you downloaded from your dashboard. Do not change it. The token and group go together and cannot be changed.
YAML Example:
Type: string
Description: Sets the logging level. Common values are info, debug, andtrace which have increasing levels of verbosity.
YAML Example:
Type: bool
Description: If set to true, logs will be output in JSON format.
YAML Example:
Type: uint64
Description: The number of concurrent scans to perform. It also drives concurrency in the Source being scanned if the source supports it. If ommitted the value defaults to the number of CPUs detected on the machine TruffleHog is running on.
YAML Example:
Type: bool
Description: If set to true, the TruffleHog will run once and exit after the scans are completed. If set to false, TruffleHog will run as a daemon.
YAML Example:
Type: List of Source objects
Description: A list of source configurations. See Scan data for secrets to learn how to add Source integrations for your providers.
YAML Example:
Type: List of Notifier objects
Description: A list of notifier configurations to handle notifications. See Notify results to learn how to add Notifier integrations for your providers
YAML Example:
Type: List of CustomRegex objects
Description: Custom regex detectors to identify secrets. See Customizing detection for more infromation
YAML Example:
Type: List of CustomVerifier objects
Description: Custom verifiers for secret verification. See On-premise verification for more infromation.
YAML Example:
Type: string
Description: The interval at which secrets are re-verified, specified as a duration (e.g., "24h" for 24 hours).
YAML Example: