This update adds support for managing a virtual layer per gateway, so a gateway when specified in the model will be responsible to create the views of the virtual layer as well as the physical tables. This is controlled by setting the provisionally called gateway_managed_virtual_layer flag to true in the config.

gateways:
  local:
    connection:
      type: postgres
      ...

  bigquery_gw:
    connection:
      type: bigquery
    variables:
      overriden_var: 'bigquery'

  snowflake_gw:
    connection:
      type: snowflake
      database: db1
      ...
    variables:
      overriden_var: 'snowflake'

default_gateway: postgres

gateway_managed_virtual_layer: true

In this case the virtual layer will be created by the specific gateway instead of using the default gateway, which means that the catalog doesn't need to be shared between the gateways. Also the gateway specific catalog will be set for each corresponding model and the gateway specific variables will take precedence over global ones for the gateway-specified in the model.

The default behaviour remains unchanged when the flag is set to false or omitted from the config.