Sometimes during development lifecycle, you don't want to update or even create a job definition out of your project files.
Some examples:
- You're going to use solely Run Submit API
- You want to update or change job definitions only when you release the job
- Multiple users working in parallel on the same job
In such use-cases, Run Submit API is much a simpler way to work with the deployments.
To deploy files without reflecting the deployment definition to jobs, do the following:
dbx deploy --files-only
To launch latest file-based deployment, do the following:
dbx launch --as-run-submit --job=<job-name>