Thanks Jordan, We are still evaluating on moving to 2.5. Do we have any workaround in 2.0
Thanks. On Thursday, February 15, 2018 at 1:13:27 AM UTC-5, Jordan Borean wrote: > > In the latest release it isn't possible to do with the current > win_scheduled_task module. For 2.5 the module was drastically rewritten and > supports this scenario, you can find the latest docs for it here > http://docs.ansible.com/ansible/devel/modules/win_scheduled_task_module.html > . > > Using your example this is how it could possibly be done with the new > format in 2.5 > > - name: create scheduled task to run every minute > win_scheduled_task: > name: task name here > actions: > - path: cmd.exe > arguments: /c echo hello world > triggers: > - type: registration > repetition: > - interval: PT1M > duration: '' # an empty value should mean it last infinitely > > > What this means is that a task that run "cmd.exe /c echo hello world" will > create a registration trigger and run that every minute indefinitely. The > registration trigger just means start the task on registration. > > Thanks > > Jordan > > -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/7e48d695-375a-45ea-b94e-20da26a657d5%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
