Advocate IAdd Git Integration Support for Tables, Views, Functions, and Stored Procedures in Lakehouses
I’m aware that Lakehouse Git integration in Microsoft Fabric is currently in preview. However, I believe some critical support is missing that would significantly enhance the usability and maturity of this feature.
At the moment, Git integration does not support versioning or tracking of critical Lakehouse objects such as:
- Tables
- Views
- User-defined functions
- Stored procedures
These objects are essential components of any data platform, and not being able to track their definitions in source control limits our ability to:
- Perform proper code reviews
- Roll back changes
- Maintain consistent environments across workspaces
- Collaborate effectively in larger teams
- Follow DevSecOps best practices
Suggestion:
Please extend Git integration in Fabric Lakehouses to include full support for these objects. For example, warehouse git integration supports all of those objects.
This enhancement would greatly improve DevOps practices in Fabric and align with modern data engineering workflows.
1 Comment
murat-toAdvocate II
I strongly agree with this idea.
Git integration for Lakehouse objects such as tables, views, functions, and stored procedures is essential for proper DevOps workflows, change management, and governance.
I would also like to add an important related point:
in order for Git integration to be truly effective, we need an official way to retrieve the canonical table definition (DDL) itself.
At the moment, DESCRIBE EXTENDED in Spark SQL can be used only as a workaround to inspect metadata, but it is not a reproducible or authoritative DDL.
This makes it difficult to:
- manage schemas as code (Schema as Code)
- review schema changes via pull requests
- track structural changes across environments
- ensure reproducibility and auditability
In traditional RDBMS platforms, features like SHOW CREATE TABLE are first-class capabilities and form the foundation of schema governance and CI/CD.
Git integration and DDL exposure should be considered complementary capabilities.
Having both would significantly improve Lakehouse schema management in enterprise environments.
Thank you for raising this important idea.
