azure-cli: Definitions created using 'az synapse spark-job-definition create' do not show in the Workspace UI with Git Integration enabled
Related command
az synapse spark-job-definition create --workspace-name <workspace> --name <job-name> --file @"folder\sparkjob.json"
Describe the bug When using ‘az synapse spark-job-definition create’ command I am able to create a sparkjob definition, however that definition is not then visible in the Synapse Workspace UI. I am however able to see it when calling ‘az synapse spark-job-definition list’
I have Git integration enabled on that workspace, checked all the branches and can’t find the job definition I’ve created in the UI.
To Reproduce
- Export existing job definition from Synapse UI
- Change jobProperties.name to be unique.
- Run `az synapse spark-job-definition create --workspace-name <workspace> --name <job-name> --file @“folder\sparkjob.json” using the previously exported file.
- Run
az synapse spark-job-definition list --workspace-name <workspace>and verify newly create job definition is visible. - Check UI.
Expected behavior The created spark job definition is also visible in Synapse Workspace UI
Environment summary
Windows-10-10.0.19044-SP0
Python 3.10.5
Installer: MSI
azure-cli 2.38.0
Extensions:
azure-cli-ml 1.41.0
Dependencies:
msal 1.18.0b1
azure-mgmt-resource 21.1.0b1
Additional context
About this issue
- Original URL
- State: open
- Created 2 years ago
- Comments: 16 (8 by maintainers)
Hi @alexszym, I tried to use cli to create other artifacts like SQL script with git enable and there is the same issue as you mentioned above. But something like spark pools that are managed by “azure-mgmt-synapse” module are good. So, I think this issue is related to git CI/CD background.
@alexszym Let me engage the synapse engineering team (CLI), before we resort to support.
@RakeshMohanMSFT I’ve tried the same script on my side without Git integration enabled and that works fine, so I think the cause of the issue might indeed be the Git integration feature.
In case its relevant, my branches are named:
main(main branch)publish(publish branch)