# Pipeline variables: inject values into extract/transform/load configs
#
# All keys here are available as ${VAR_NAME} in extract.yaml, load.yaml,
# transform.yaml, and pipeline.yaml. Use ${VAR:-default} for optional vars.
#
# Precedence: env vars and CLI --var flags override values in this file.
#
# Usage:
#   Pipeline.from_config_dir("data/etl_examples")  # loads variables.yaml automatically
#   Pipeline.from_config_files(..., variables="data/etl_examples/variables.yaml")
#   Pipeline.from_config_file("data/etl_examples/pipeline.yaml")  # can also embed a "variables" section

# Paths used by extract.yaml and load.yaml (defaults match relative paths from repo root)
INPUT_PATH: data/etl_examples/input.csv
OUTPUT_PATH: data/etl_examples/output.csv

# Example: override when API runs from a different working directory
# INPUT_PATH: /absolute/path/to/pycharter/data/etl_examples/input.csv
# OUTPUT_PATH: /absolute/path/to/pycharter/data/etl_examples/output.csv

# Example: common variables you might inject for other pipeline types
# API_KEY: your-api-key-here
# DATABASE_URL: postgresql://user:pass@localhost:5432/mydb
# BATCH_SIZE: "5000"
# ENVIRONMENT: development
