| `api_page_limit` | | `None` | Limit on ingested dashboards and charts API pagination. |
| `skip_draft` | | `true` | Only ingest published dashboards and charts. |
| `dashboard_patterns.allow` | | | List of regex patterns for dashboards to include in ingestion. |
| `dashboard_patterns.deny` | | | List of regex patterns for dashboards to exclude from ingestion. |
| `chart_patterns.allow` | | | List of regex patterns for charts to include in ingestion. |
| `chart_patterns.deny` | | | List of regex patterns for charts to exclude from ingestion. |
| `env` | | `"PROD"` | Environment to use in namespace when constructing URNs. |
| `parse_table_names_from_sql` | | `false` | See note below. |
Note! The integration can use an SQL parser to try to parse the tables the chart depends on. This parsing is disabled by default,
but can be enabled by setting `parse_table_names_from_sql: true`. The default parser is based on the [`sql-metadata`](https://pypi.org/project/sql-metadata/) package.
As this package doesn't officially support all the SQL dialects that Redash supports, the result might not be correct. You can, however, implement a
custom parser and take it into use by setting the `sql_parser` configuration value. A custom SQL parser must inherit from `datahub.utilities.sql_parser.SQLParser`
and must be made available to Datahub by ,for example, installing it. The configuration then needs to be set to `module_name.ClassName` of the parser.