Hi.

We have a range of scheduled jobs and _one_ continuous job all defined in .yml and deployed with DAB. The continuous job is paused per default and we use a scheduled job of a notebook to pause and unpause it so that it only runs during business hours. The issue is that if we want to deploy changes to existing scheduled jobs or a new job, it'll override the status defined by the notebook with the paused status defined in the .yml file. 

It seems it's possible to define which jobs to deploy with the "include" key in the databricks.yml file, but as we have _many_ scheduled jobs and _one_ continuous job, this seems a rather circumstantial solution both to implement but also to maintain. Isn't it possible to negate the include definition, which would be a lot more elegant? Is there another solution I am not aware of?

Thanks in advance for any contribution.