Hi I would like to parametrize the source names based on the Meltano #troubleshooting

Hi, I would like to parametrize the source names b...

simone_gaiarin

02/08/2023, 2:53 PM

Hi, I would like to parametrize the source names based on the environment. For example in

prod

my source is called

my_source

, while in

dev

my source is called

my_source_smith

(smith is the last name of the developer). The developer is defined in a

DEVELOPER

environment variable. What is the best way to achieve this? Does it make sense to parametrize the sources (the idea is to make the dev environments completely independent among develpers)? Hi. I would like to parametrize my sources so that in the

edgar_ramirez_mondragon

02/08/2023, 6:18 PM

Hi @simone_gaiarin, do you mean dbt sources?

simone_gaiarin

02/10/2023, 1:20 PM

Ops, I'me realizing now I've posted in the wrong slack, I wanted to post on dbt. 🙂 Yes I mean dbt sources.

edgar_ramirez_mondragon

02/10/2023, 3:54 PM

So, I’m not sure but I’ve shared this in #C01UW21TM98 in case anyone in the community knows

simone_gaiarin

02/13/2023, 7:58 AM

thanks

simone_gaiarin

02/13/2023, 8:02 AM

My current solution is this: source:

Copy code

version: 2

sources:
  - name: "mysource{{ env_var('DATASET_SUFFIX', '') }}"

model:

Copy code

with

source as (

    select *
    from {{ source(source_name('mysource'), 'mytable') }}

),

macro:

Copy code

{% macro source_name(the_name) %}{{ the_name + env_var('DATASET_SUFFIX', '') }}{% endmacro %}%

I couldn't figure out a way to create a macro/function to use in the source.yml instead of using env_var directly

2 Views

Open in Slack

Previous Next