Sqlmesh integration

[dbrtly]

What's the use case?

Similar to the existing dbt integration.
The integration should register models in a sqlmesh project and assets in a dagster project foend to end visibility.

Ideas of implementation

Similar to dbt.

One generic asset definition that enables a library and interprets the sqlmesh models as dagster assets.

Additional information

No response

Message from the maintainers

Impacted by this issue? Give it a 👍! We factor engagement into prioritization

[AlaaInflyter]

Hey there !
Any news on this ?

[dbrtly]

Regarding the design, I would anticipate that the key diff vs dbt is state management. Dbt uses manifest.json, while sqlmesh writes to a sqlmesh schema in your data warehouse or the scheduler's db.

https://sqlmesh.readthedocs.io/en/stable/guides/connections/#overview

My intuition is that we would extend the db_resource to get equivalent asset definitions initially. Agreed?

[AlaaInflyter]

There's also how environments are handled.
For example: currently, Dagster's docs recommends using cloned DBs, and then you'd make DBT use the correct db depending on the environment.
Since Sqlmesh has a different approach to envs with its plans, there might be need to adjust this recommendation when using sqlmesh?