win_scheduled_task : run the scheduled task every minute

1,484 views
Skip to first unread message

ktesr...@gmail.com

unread,
Feb 14, 2018, 5:13:01 PM2/14/18
to Ansible Project
Team,

Is there any option to run the scheduled task every minute. in the documentation i see the frequency is either once or daily or weekly

I am referring to "Advance Settings" from Trigger of Windows Scheduled task

Thanks.

Jordan Borean

unread,
Feb 15, 2018, 1:13:27 AM2/15/18
to Ansible Project
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

ktesr...@gmail.com

unread,
Feb 15, 2018, 11:31:28 AM2/15/18
to Ansible Project
Thanks Jordan,

We are still evaluating on moving to 2.5. Do we have any workaround in 2.0

Thanks.

Jordan Borean

unread,
Feb 15, 2018, 4:11:34 PM2/15/18
to Ansible Project
Not in any easy idempotent way unfortunately, you have some options, you could;

* Use win_command/win_shell to create the task but the COM API used can get quite complex and dealing with idempotency would be difficult
* You can copy the newer version of the module https://github.com/ansible/ansible/blob/devel/lib/ansible/modules/windows/win_scheduled_task.ps1 to a directory called library and use it like you would when 2.5 is out. It is best to name the module with a special suffix so you know that it is a custom version and not the builtin module used in Ansible.

Thanks

Jordan

ktesr...@gmail.com

unread,
Feb 16, 2018, 2:19:48 PM2/16/18
to Ansible Project
Thanks Jordan i will go ahead with your suggestion
Reply all
Reply to author
Forward
0 new messages