Environment Variables
Credentials and connection details stay outside the manifest. v0.3.0 reads the process environment and, if present, .agoraform.env next to the selected manifest. Process environment variables always win.
Never put these values in YAML, plan output, logs, or agoraform.state.json.
Matomo
Section titled “Matomo”| Variable | Required | Description |
|---|---|---|
MATOMO_URL | yes | Matomo base URL, for example https://matomo.example.com |
MATOMO_TOKEN_AUTH | yes | API token |
MATOMO_SITE_ID | for site resources | Numeric site ID |
MATOMO_CONTAINER_ID | for Tag Manager | Tag Manager container ID |
Google Ads
Section titled “Google Ads”| Variable | Required | Description |
|---|---|---|
GOOGLE_ADS_DEVELOPER_TOKEN | yes | Google Ads API developer token |
GOOGLE_ADS_CLIENT_ID | yes | OAuth 2.0 client ID |
GOOGLE_ADS_CLIENT_SECRET | yes | OAuth 2.0 client secret |
GOOGLE_ADS_REFRESH_TOKEN | yes | OAuth 2.0 refresh token |
GOOGLE_ADS_CUSTOMER_ID | yes | 10-digit customer ID (hyphens optional) |
GOOGLE_ADS_LOGIN_CUSTOMER_ID | no | Manager-account customer ID |
Loading .agoraform.env
Section titled “Loading .agoraform.env”When Agoraform starts, it looks for .agoraform.env next to the selected manifest. With the default agoraform.yaml, that is the current directory. With -f path/to/agoraform.yaml or a positional manifest path, Agoraform loads path/to/.agoraform.env. If the file is absent, environment-variable behavior is unchanged.
See project structure for file format and security guidance.