[FEATURE] support item-definition for lakehouse items

[Guust-Franssens]

Use Case / Problem

Lakehouse item now supports item definition, this means that now the CLI should support import and export for lakehouse item_type.

This would simplify CI/CD scenarios where you are looping over a folder with Fabric items and deploying using the import command. Currently you need to separately handle the lakehouse item.

In addition the current error message for non-supported import items isn't super clear.

fab import ws1.workspace/lh1.lakehouse -i ./src/lh1.Lakehouse/
x import: [UnsupportedCommand] not supported for command 'import'

Proposed Solution

Remove code restriction on import and export for lakehouses as it is now supported.

Alternatives Considered

Current workaround is to check the item type when deploying from a folder and if type == "lakehouse" then use mkdir instead. However it would be better to use import as then you can use the full definition

Impact Assessment

• This would help me personally
• This would help my team/organization
• This would help the broader fabric-cli community
• This aligns with Microsoft Fabric roadmap items

Implementation Attestation

• I understand this feature should maintain backward compatibility with existing commands
• I confirm this feature request does not introduce performance regressions for existing workflows
• I acknowledge that new features must follow fabric-cli's established patterns and conventions

Implementation Notes

I have made the following minor changes locally and to make the import for lakehouse works:

• removed

  fabric-cli/src/fabric_cli/commands/fs/impor/fab_fs_import_item.py

  Lines 32 to 37 in 1fce5c0

  	# Input path only support from local directories
  	if input_path["type"] == "lakehouse":
  	raise FabricCLIError(
  	"Import from Lakehouse/Files not supported",
  	fab_constant.ERROR_NOT_SUPPORTED,
  	)

• added lakehouse here
  

  fabric-cli/src/fabric_cli/core/fab_config/command_support.yaml

  Lines 249 to 269 in 1fce5c0

  	import:
  	supported_items:
  	- report
  	- spark_job_definition
  	- semantic_model
  	- notebook
  	- kql_dashboard
  	- data_pipeline
  	- kql_queryset
  	- eventhouse
  	- kql_database
  	- mirrored_database
  	- reflex
  	- eventstream
  	- mounted_data_factory
  	- environment
  	- copy_job
  	- variable_library
  	- graph_ql_api
  	- dataflow
  	- sql_database

  
  and here
  

  fabric-cli/src/fabric_cli/core/hiearchy/fab_item.py

  Lines 105 to 122 in 1fce5c0

  	case (
  	ItemType.REPORT
  	| ItemType.SEMANTIC_MODEL
  	| ItemType.KQL_DASHBOARD
  	| ItemType.DATA_PIPELINE
  	| ItemType.KQL_QUERYSET
  	| ItemType.EVENTHOUSE
  	| ItemType.KQL_DATABASE
  	| ItemType.MIRRORED_DATABASE
  	| ItemType.REFLEX
  	| ItemType.EVENTSTREAM
  	| ItemType.MOUNTED_DATA_FACTORY
  	| ItemType.COPYJOB
  	| ItemType.VARIABLE_LIBRARY
  	| ItemType.GRAPHQLAPI
  	| ItemType.DATAFLOW
  	| ItemType.SQL_DATABASE
  	):

[HasanAboShally]

/triaged

Hi @Guust-Franssens,

Thanks for the detailed issue and the thorough implementation notes — really appreciate you digging into the code and identifying the exact changes needed! 🙏

You're right that Lakehouse now supports item definitions, and we should enable import/export for it. Would you be interested in submitting a PR with your changes? We'd be happy to review and merge it.

---

On a related note, since you're clearly working on CI/CD scenarios, I wanted to share some upcoming work that might be relevant to you:

1. Bulk Import/Export — We're actively working on enabling bulk import and export capabilities within the CLI. This will allow you to work with multiple items at once, which should simplify your folder-based deployment loops.

2. Deploy Command — We're also working on an integration with the Fabric CI/CD library and plan to introduce a deploy command directly from within the CLI. This command would handle rewrites, rebinding, and connecting items across environments automatically.

These features should make CI/CD workflows much smoother. Happy to keep you posted on progress!

Looking forward to your PR if you'd like to contribute the Lakehouse support. 🚀

[microsoft-github-policy-service]

Triage has been completed for this issue.

[Guust-Franssens]

Hey @HasanAboShally 👋 !
I am happy to make a PR for this however most likely won't be able to work on it this week so if anyone else wants to tackle it feel free. Perhaps best to tag the issue with "help wanted"

Those upcoming CI/CD changes seem great! Curious how the integration with the CI/CD library will work, will it become a dependency or CLI will cherry pick some things over, or something else?

[HasanAboShally]

Hi @Guust-Franssens,

No worries on the timing — I'll add the help wanted label so others can pick it up if they'd like. If not, we can circle back to you when you have bandwidth, or we might tackle it ourselves. 👍

On the CLI + Fabric CI/CD library integration:

Great question! The plan for now is to add the Fabric CI/CD library as a dependency of the CLI. This means:

• The CLI will expose a deploy command that leverages the library's capabilities under the hood
• You get the best of both worlds: CLI for setup/scripting/interactive work (the CI part), and the library's deployment logic for rewrites, rebinding, and dependency handling (the CD part)
• This keeps the CLI lightweight — we're not reinventing the wheel, just providing a convenient entry point to the library's functionality

The idea is that you can do your full CI/CD flow without leaving the CLI — or mix and match with your existing pipelines as needed. Still working through some details, but that's the direction.

Does this align with what you had in mind? Happy to hear any thoughts or requirements from your side!