[BUG] Enviroments, when importing environment enable_native_execution_engine is skipped

[edkreuk]

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

[ayeshurun]

Hi @edkreuk,

Thank you for raising this.

We acknowledge this is currently a functional gap. The CLI currently relies on spark compute update and publish environment APIs rather than utilizing the standard Create Item with Definition API. Consequently, full support for Environment definitions is not yet available.

We will address this limitation in the upcoming releases to ensure full alignment with the ci-cd definition model.