filipe-asilva/Run Elementary
Monitor your dbt project and be the first to know of data issues.
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Stale
- License
- None
Inputs
| name | description | required | default |
|---|---|---|---|
| warehouse-type | The type of your warehouse (snowflake, bigquery, redshift, etc) | yes | — |
| adapter-version | The dbt-adapter version that should be used (1.5.0 for example). If not provided, the latest version will be used. | no | — |
| project-dir | The path to your dbt project dir. You should pass this parameter if the dbt project dir is not located in the current directory (normally the repository root) - the EDR command will run with this directory as the working directory. | no | — |
| profiles-yml | The content of dbt's `profiles.yml` with the `elementary` profile. This is optional if you already have a `profiles.yml` in your repository or in ~/.dbt. Can be generated by running `dbt run-operation elementary.generate_elementary_cli_profile` within your project. | no | — |
| edr-command | The command to run, for example `edr monitor --slack-webhook <SECRET_SLACK_WEBHOOK>`. | yes | — |
| profile-target | Target profile used for internal dbt calls. If your `edr_command` uses the `--profile-target` or `--project-profile-target` flags, please set this attribute to the value of those flags. | no | — |
| bigquery-keyfile | The content of your BigQuery keyfile. | no | — |
| gcs-keyfile | The content of your Google service account keyfile, for usage with Google Cloud Storage. | no | — |
Outputs
no outputs