- 
                Notifications
    
You must be signed in to change notification settings  - Fork 15
 
Deploy dbt-docs with Metabase references (exposures) #3803
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
8da8493    to
    71b1f07      
    Compare
  
    | 
           Can we update the pyproject.toml to use dbt-metabase=1.5.0. My install was using 0.10.3 and throwing errors. Also, how do we authenticate?  | 
    
| 
           @vevetron You need a metabase API key. Evan has access to it.  | 
    
71b1f07    to
    9a70fc2      
    Compare
  
    65c8abb    to
    7a4d99d      
    Compare
  
    1032154    to
    7924797      
    Compare
  
    9b1e847    to
    3469430      
    Compare
  
    db29d75    to
    142a58d      
    Compare
  
    2e00a5b    to
    db07ce0      
    Compare
  
    e994296    to
    eba4cfd      
    Compare
  
    f9b0531    to
    0c64589      
    Compare
  
    dbef0f6    to
    8810220      
    Compare
  
    8810220    to
    b2839cb      
    Compare
  
    | 
           We found out this week that Exposures have been use to configure models that are published to Open Data Portal. So we should not add Metabase exposures to our code base to avoid conflicts.  | 
    
b2839cb    to
    ae0e59a      
    Compare
  
    …etabase exposures and update dbt docs
ae0e59a    to
    05c2960      
    Compare
  
    
Description
There is always a question about where dbt models have been used in Metabase. When working on synchronizing Metabase, @ohrite and I learned about "exposures" in dbt-metabase.
This PR creates a workflow that extracts exposures from Metabase and generate dbt-docs to be visualized in Cal-ITP dbt docs.
The workflow runs every Monday at 8am UTC (1am PST) or when there is any changes on model merged to the main branch.
Type of change
How has this been tested?
It was tested running locally and then through the workflow.
Post-merge follow-ups