Git Server Proxy won't stay up

[Scanning]

We are running a job with multiple tasks that require the Git Server Proxy to remain operational for the entire duration of the job.

Since each task may need access to the proxy, and job runtimes vary from brief to several hours, what is the best approach to ensure the Git Server Proxy remains available throughout the job, aside from setting the auto-termination time to the maximum possible duration?

[Stefan-Koch]

You could add a task, where you start/stop your proxy cluster with databricks cli.

another consideration:
Do you even need the cluster if you're running a job? I assume that the job refers to code in a Git folder? Instead of the Git approach, you could deploy the code artifacts with asset bundles. That way, when you start a job, you don't need a Git proxy cluster

[Scanning]

The Git Server Proxy is needed for various tasks within the job, and multiple jobs may rely on it. Manually terminating it at the end of job1 could lead to job2 failing.