To have a job both in development and production, we continue to recommend defining at the top level of the configuration, under the "resources" field. What you're looking for, which, if I understand correctly, is to deploy a job only to dev+stg but ...
@_escoto You can achieve this by defining the entire job in the "targets" section for your development target. Resources defined in the top-level "resources" block are deployed to all targets. Resources defined both in the top-level "resources" block...
Hi Breno,
If the jobs you're deploying are similar, it sounds like a good fit for target overrides. You'd define the core of the job just one, and specialize it on a per-target basis. For example, you could define a "eu" and "na" target, each pointin...
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 depl...
If the jobs you're defining per customer are completely different and don't share anything (e.g. some base configuration), then using targets for this purpose is not a great fit.
If you're looking to share files between these bundles (maybe some note...
