Not able to edit_mode UI_LOCKED to EDITABLE in bundle deployment for development mode

[kishanmaladkar]

The edit_mode for Databricks jobs cannot be overridden using the bundle. 

Based on the jobs REST API docs, there is a functionality to set this parameter but in the bundle docs, it's not available. 

How can I use this in the bundle to override the parameters? Also, note that this job calls other jobs - this is an E2E workflow where training, scoring, and validation jobs are called inside the workflow. 

Below is the config of the job. 

resources:
  jobs:
    <job_name>:
      name: ...
      job_clusters:
        - job_cluster_key: ...
      max_concurrent_runs: 10
      tasks:
        - task_key: ...
        - task_key: ...
        - task_key: ...
          run_job_task:
            job_id: ...
        - task_key: ...
        - task_key: ...
          run_job_task:
            job_id:  ...
            job_parameters:
              ...
      git_source:
        git_url: ${var.git_repo}
        git_provider: gitHubEnterprise
        git_branch: ${var.git_branch}
      queue:
        enabled: true
      parameters:
        - name: ...
          default: ...
        - name: ...
          default: ...
        ...
      tags:
        project: ...
        stage: ${bundle.target}
        team: ...
      edit_mode: EDITABLE

[Walter_C]

When you refer you cannot edit it, do you refer to this specific field for the edit mode, it keeps blocked as UI_LOCKED or the option is just not available?

[kishanmaladkar]

edit_mode is not mentioned in the bundle docs, I saw this mentioned API Job create docs. 
I tried using it in the bundle but it did not override it. 

I am unsure if this option is available through the bundle but I am trying to find a way to change it from UI_LOCKED to EDITABLE similar to how it can be achieved through Job Create API. 

[pietern]

The `edit_mode` property cannot be set by design. It is set to `UI_LOCKED` on bundle deployment to let viewers of the job in the UI know that any changes they make to the job instance are going to be clobbered the next time someone runs a bundle deploy.