Based on the knowledge sources, I can provide you with examples of how to structure your

config.yml

file. However, I need to clarify some important points: ## Important Limitations According to the documentation, the

config.yml

file is primarily used for configuring alerts (specifically Slack integration settings). [Most other CLI arguments cannot be configured in

config.yml

](https://slack.com/archives/C02CTC89LAX/p1736350825518229) and must be passed as CLI flags or environment variables. ## What CAN Be Configured in config.yml Based on your commands, here's what you can configure in `config.yml`:

yaml slack:   token: <slack_token>   channel_name: <slack_channel_name>   group_alerts_by: "table"  # optional timezone: <optional_timezone_for_timestamps>

The

config.yml

file should be located at:

HOME_DIR/.edr/config.yml

## What CANNOT Be Configured in config.yml The following arguments from your commands cannot be set in

config.yml

and must be passed as CLI flags or environment variables: -

--profiles-dir

-

-t

(profile target) -

--env

-

--days-back

-

--gcs-bucket-name

-

--disable-samples

-

--suppression-interval

## Alternative: Environment Variables You can use [environment variables](https://docs.elementary-data.com/oss/cli-commands#cli-options) for CLI options in the format

EDR_<COMMAND>_<OPTION>=<VALUE>

. For example:

bash export EDR_SEND_REPORT_PROFILES_DIR="<profiles-dir>" export EDR_SEND_REPORT_ENV="<env>" export EDR_SEND_REPORT_DAYS_BACK="<days_back>"

Note: Environment variables [cannot be directly referenced in

config.yml

](https://slack.com/archives/C02CTC89LAX/p1736350825518229) using syntax like

${VARIABLE_NAME}

. ## Recommended Approach For your use case, I recommend: 1. Use

config.yml

for Slack configuration only 2. Pass other arguments via CLI flags or environment variables 3. For sensitive values like

--slack-token

, use CLI flags with environment variables:

--slack-token $SLACK_TOKEN