Transformations: Allow for target-based deployment.yml specifications
deployment.yml is not configurable using Jinja2 templating or any of it's utilities.
In case we want to have 2 separate schedules for a multi-destination project, we're unable to achieve that using deployment.yml as it is right now.
It would be great to be able to either template it with jinja or have target-specific configuration, for example:
jobs:
<target-name>:
name-1:
<target-name2>:
name-2:
Please sign in to leave a comment.
Comments
0 comments