Should I be able to pass different extra_vars on a scheduled task than are present on the template?
For instance, I have a database name on a template called “foo” and when i create a scheduled job for it, I see “foo” passed from the original template. However, if I change this on the scheduled job and press save - it reverts back to whatever the template has. Anyone experience this?
The reason why this would be useful is that I have a generic playbook that can be passed extra args to perform backups in various environments. Not being able to schedule these with different vars requires me to clone the template, which is a bit messy. Having the variables show up on a scheduled task makes it seem like these should be changeable.