added macro for wh selection

[McKnight-42]

resolves #438

Description

take over pr: #115 to get pre-commit issues taken care of and ready for merge

Checklist

• I have read the contributing guide and understand what's expected of me
• I have signed the CLA
• I have run this code in development and it appears to resolve the stated issue
• This PR includes tests, or tests are not required/relevant for this PR
• I have opened an issue to add/update docs, or docs changes are not required/relevant for this PR
• I have run changie new to create a changelog entry

[McKnight-42]

curious if anyone has an idea as to why this causes a
dbt/adapters/snowflake/impl.py:80: error: Incompatible types in assignment (expression has type "AttrDict", variable has type "str") [assignment] error? seems same as all implementations in dbt-core I could find. just curious if there is better path than the ignore

[mikealfare]

It's silly, but you can remove the type annotation from warehouse and mypy will be happy; you can also update it to Any. The issue is that self.execute_macro() lists the type for kwargs as Dict[str, Any]. mypy doesn't like it when you make the type more strict (str is a proper subset of Any).

[McKnight-42]

oh that's interesting iI didn't think the type value for the "warehouse" input would bother the previously defined one for execute_macro thank you for clearing that up @mikealfare

[mikealfare]

Is this a supported format? I feel like our process to roll up change logs might not like this. Based on the timestamp, it might be an older format.

[McKnight-42]

This part might be from before some more recent changes to our changie logic so yeah can remove

[manugarri]

@McKnight-42 nice! after some trial and error I managed to get it working on prerelease v1.5.0b3 , is there any timeline to when is gonna be released on pypi?

[McKnight-42]

@manugarri we did some releases yesterday actually https://pypi.org/project/dbt-snowflake/1.5.0b3/ I believe this should be apart of that release

[manugarri]

Awesome, great! One question I have, is it not possible to access environment variables inside this macro?

im trying to return different warehouses depending on the snowflake user running dbt, this is what i have so far

    {% set warehouses_specs = {
            "user1": {
                "SMALL": "wh1_small",
                "LARGE": "wh1_large"
            },
            "user2": {
                "SMALL": "wh2_small",
                "LARGE": "wh2_large"
            }
        }
    %}

    {{ return(warehouses_specs[env_var('SNOWFLAKE_USER')][warehouse] ) }}
{%- endmacro %}

however when i do dbt run i get these weird error:
'MacroManifest' object has no attribute 'env_vars'

How could I read the current_user inside this macro?

For what I can tell, it seems that you cant read env_vars from inside this macro.

For example, this macro definition throws the exception

{% macro snowflake_warehouse(warehouse) -%}
  {% set foo = env_var('SNOWFLAKE_USER') %}
  {{ return(warehouse) }}
{%- endmacro %}

while this one doesnt

{% macro snowflake_warehouse(warehouse) -%}
  {{ return(warehouse) }}
{%- endmacro %}

UPDATE: After a lot of help from dylan at the dbt slack channel, this particular use case (using the snowflake user to decide which warehouse to run) can be solved by using target.user.

However, there seem to be a bug with the implementation that makes it impossible to reference environment variables in this particular macro

[McKnight-42]

after some more digging we have decided for now to actually revert #503 we now think that this method is the wrong way as it allows for some unintended consequences and will be trying to find a better way forward. sorry for any inconvenience this causes