🎉 What's new

Announcing some exciting updates for the Atlan dbt action in GitHub:

• Environment-based mapping — If you have set up different branches for your dbt environments, you can now map your branch name with the dbt environment name and Atlan will fetch downstream assets for that specific environment. Use the DBT_ENVIRONMENT_BRANCH_MAP input in the GitHub action config to map dbt environments to branches and keep everything in sync!
• Materialized asset details in comment header — You can now easily access a link to the materialized asset along with the environment and project name in the comment header to get the context you need for materialized assets.
• Ignore alias — You can also use the IGNORE_MODEL_ALIAS_MATCHING input in the Github action config to ignore matching model names through aliases. This will allow you to fetch the downstream impact of the dbt models based on the file name instead of the alias.

... and some bug fixes to boost your workflow:

• Detect new models — Previously, when a new model was added that was not yet present in Atlan, the dbt action used to break. Now you'll be notified if a new model has been added and view the downstream impact once the asset has been cataloged in Atlan.
• Limit the list of downstream assets to 100 — If you've got assets with extensive lineage, we've got your back! We've limited the list of downstream assets to 100, so you no longer need to worry about hitting the GitHub comment character rate limit.
  

To learn more, see How to add impact analysis in GitHub.

Get started with exploring the updates and happy dbt-ing! 🎉