Skip to main content

Overview

The Valiqor SDK resolves configuration from three sources, in priority order:
  1. Programmatic — Parameters passed to ValiqorClient(...) or get_config(**overrides)
  2. Environment variablesVALIQOR_API_KEY, VALIQOR_PROJECT_NAME, etc.
  3. Config file.valiqorrc (JSON file, auto-discovered from cwd upward)
Higher-priority sources override lower-priority ones. For example, passing api_key="..." to the constructor always wins over the environment variable.

.valiqorrc File

A JSON configuration file placed in your project root (or any parent directory). The SDK walks up from the current directory to find it.
Never commit API keys to version control. Use environment variables for production deployments.

Environment Variables


Configuration Functions

get_config()

Resolve the full configuration from all sources.
With overrides:

Config Keys & Defaults


find_config_file()

Find the nearest .valiqorrc file by walking up from the given path.

load_config_file()

Load and parse a .valiqorrc file.

save_config()

Write configuration to a .valiqorrc file.
Returns: boolTrue if saved successfully.

ensure_output_dirs()

Create the trace and scan output directories if they don’t exist.

should_upload()

Check if the current config enables cloud uploads.

Constants


Module-Level configure()

The top-level valiqor.configure() function provides a convenient shortcut:

Example: Production Setup