Summary
Users sometimes assume Cosmos only works with warehouses that have a built-in ProfileMapping (Snowflake, BigQuery, Redshift, Databricks, …), and fall back to running dbt in a plain BashOperator for adapters like dbt-glue. In fact, Cosmos can run any dbt adapter when the user supplies their own profiles.yml via ProfileConfig(profiles_yml_filepath=...) — see Use your own profiles.yml.
Ask
- Add an explicit note (on the profile-mapping / supported-databases docs) that adapters without a built-in
ProfileMapping are still fully supported via a user-provided profiles.yml.
- Add a short dbt-glue example using
ProfileConfig(profiles_yml_filepath=...).
Why
Running dbt via BashOperator loses Cosmos's task-group rendering and OpenLineage lineage; documenting the bring-your-own-profiles.yml path steers these users to Cosmos instead.
Good first issue
Docs-only change — see the existing guide linked above for the pattern.
Internal reference (Astronomer): Zendesk #92947 — https://astronomer.zendesk.com/agent/tickets/92947 (agent-only link).
Summary
Users sometimes assume Cosmos only works with warehouses that have a built-in
ProfileMapping(Snowflake, BigQuery, Redshift, Databricks, …), and fall back to running dbt in a plainBashOperatorfor adapters like dbt-glue. In fact, Cosmos can run any dbt adapter when the user supplies their ownprofiles.ymlviaProfileConfig(profiles_yml_filepath=...)— see Use your own profiles.yml.Ask
ProfileMappingare still fully supported via a user-providedprofiles.yml.ProfileConfig(profiles_yml_filepath=...).Why
Running dbt via
BashOperatorloses Cosmos's task-group rendering and OpenLineage lineage; documenting the bring-your-own-profiles.ymlpath steers these users to Cosmos instead.Good first issue
Docs-only change — see the existing guide linked above for the pattern.
Internal reference (Astronomer): Zendesk #92947 — https://astronomer.zendesk.com/agent/tickets/92947 (agent-only link).