Ben Cassell

As you suspect, this is currently a limitation of the platform. I've raised the issue internally, but can't commit to a timeline yet. Thanks for your report.

@jeremyyeo yes, pretty much. I haven't written a macro for it, but that's basically what I do internally in places where dbt expects us to be able to execute multiple...

Thanks for the reports. I merged a PR from @stevenayers-bge yesterday that in principle allows configuration of the other necessary piece (now both redirect url and scopes can be configured),...

This is already possible without a macro. The compute definitions are per 'output' in your profile, so just use the same tag with a different definition that's matched to each...

That's a good question that I don't know the answer to off the top of my head. I recommend experimenting with a SQL comment like: ``` -- {{ target.compute.small_tables.http_path }}...

We do not support this; you might be able to set these params as part of python models or with a pre-hook using SET, but I've not tested either method.

This is pretty far from what we are trying to accomplish with this library, and opens the door for many more hard to debug scenarios. Honestly, I don't see us...

We're mainly focused on providing a consistent, reliable experience across SQL Warehouse (including serverless) and All-Purpose clusters. Providing this config capability is technically feasible, but as I'm the only one...

Job clusters are only supported for python models as they do not have a Thrift server on them (a pre-req for the way we execute SQL). And yes, I'm happy...

Yeah, it is unofficially supported, as a.) we inherited the code, and b.) it's a completely separate path that isn't tested. However, enough people ask about it that at this...