microsoft / microsoft/fabric-cli
[BUG] Enviroments, when importing environment enable_native_execution_engine is skipped
@ayeshurun is already working on this.
Since Jan 12, 2026.
- Dominant language
- Python
- Stars
- 173
- Forks
- 63
- Avg merge
- 2d 19h
- Merged PRs (30d)
- 4
Description
Bug Description
when importing environment the option in the sparkcompute.yml enable_native_execution_engine is skipped or ignored. We can't programmatically enable this right now for customers
fabric-cli version
1.3.1
Python version
3.11
Operating System
Windows
CLI Mode
Interactive mode
Authentication Method
Interactive browser login
Steps to Reproduce
Import environment with the following setting in the sparkcompute.yml
enable_native_execution_engine: true
driver_cores: 8
driver_memory: 56g
executor_cores: 8
executor_memory: 56g
dynamic_executor_allocation:
enabled: true
min_executors: 1
max_executors: 2
runtime_version: 1.3
After importing you will see that the enable_native_execution_engine is still on False
Expected Behavior
enable_native_execution_engine is on true
Actual Behavior
enable_native_execution_engine staus on False
Additional Context
No response
Possible Solution
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.