How to migrate from dbt to Atlan action

The dbt-action is a custom action designed to perform impact analysis on changes to your dbt models in a GitHub or GitLab repository. Atlan plans to enhance this custom action to provide additional capabilities, such as impact analysis for data contracts and more.

Instead of creating separate custom actions for each new capability, Atlan has renamed the dbt-action to atlan-action to better reflect the multiple capabilities on offer and will eventually deprecate the dbt-action.

If you're currently using the dbt-action, Atlan strongly recommends migrating to the atlan-action.

Migration notice and timeline

Atlan is providing you with a window of over six months to complete the migration, with a deadline set for June 2025. However, rest assured that Atlan will not archive the dbt-action until every organization has successfully transitioned to the atlan-action.

If you choose not to migrate, please be aware that the dbt-action will no longer receive any updates. This means no new fixes or features will be implemented.

Impact of migration

You can expect a seamless transition — there will be no changes in terms of functionality. Your workflows will continue to operate as usual post-migration.

Migrate to Atlan action

GitHub

To migrate to the atlan-action:

1. Open your GitHub workflow file that currently uses the dbt-action.
2. Replace the dbt-action@v1 with atlan-action@v1 as follows:

   name: Atlan action
   
   on:
     pull_request:
       types: [opened, edited, synchronize, reopened, closed]
   
   jobs:
     get-downstream-impact:
       name: Get Downstream Assets
       runs-on: ubuntu-latest
       steps:      
         - name: Checkout
            uses: actions/checkout@v4
         
         - name: Run Action
   -        uses: atlanhq/dbt-action@v1
   +        uses: atlanhq/atlan-action@v1
           with:
             GITHUB_TOKEN: ${{secrets.GITHUB_TOKEN}}
             ATLAN_INSTANCE_URL: ${{secrets.ATLAN_INSTANCE_URL}}
             ATLAN_API_TOKEN: ${{secrets.ATLAN_API_TOKEN}}
   

GitLab

To migrate to the atlan-action:

1. Open your GitLab workflow file .gitlab-ci.yml that currently uses the dbt-action.
2. Clone v1 tag of atlan-action instead of the main branch of dbt-action:

   stages:
     - get-downstream-impact
   
   get-downstream-impact-open:
     stage: get-downstream-impact
     image: node:20
     script:
   -   - git clone https://github.com/atlanhq/dbt-action.git
   +   - git clone --branch v1 https://github.com/atlanhq/atlan-action.git
   -   - cd dbt-action
   +   - cd atlan-action
       - npm install
       - npm run build
       - node ./adapters/index.js
     environment:
       name: get-downstream-impact
     rules:
       - if: '$CI_PIPELINE_SOURCE == "merge_request_event"'
       - if: '$CI_COMMIT_BRANCH && $CI_OPEN_MERGE_REQUESTS'
         when: never
       - if: '$CI_COMMIT_BRANCH'