Be able to trigger cron remotely and asynchronously

[odain-cbd]

Goal

With this PR come 2 endpoints to deal with cron remotely and asynchronously. the idea is to execute cron.php with other PHP settings than iTop Webapp. And to avoid timeout issues for a script meant to last minutes...

1. launch_cron_asynchronously

Parameters:

• auth_user/ auth_pwd: credentials as usual
• cron_log_file: cron output file. when not provided, default value is 'cron.log'
• cron_cli_parameters: base64 encoded CLI parameters

curl -X POST -F 'version=1.3' -F "cron_cli_parameters=$CLIPARAM" "$ITOP_URL/webservices/launch_cron_asynchronously.php?version=-F 'auth_user=LOGIN' -F 'auth_pwd=PWD' {"message":"OK"}

2. cron_status

Parameters:

• auth_user/ auth_pwd: credentials as usual
• cron_log_file: cron output file. when not provided, default value is 'cron.log'

curl -X POST -F 'version=1.3' -F "cron_cli_parameters=$CLIPARAM" "$ITOP_URL/webservices/cron_status.php?version=1.3&verbose=1" -F 'auth_user=LOGIN' -F 'auth_pwd=PWD' {"status":"stopped","message":"+---------------------------+---------+---------------------+---------------------+--------+-----------+\nExiting: 1760952914 (2025-10-20 11:35:14)"}

Warning:
It is not compatible with WINDOWS.

[Hipska]

Shouldn't this better be implemented as an option/argument on the current cron.php instead of yet another endpoint?

[odain-cbd]

I will take your point when team will discuss this enhancement

[Hipska]

And why do you always close/reopen PRs? 😛

[odain-cbd]

And why do you always close/reopen PRs? 😛

50% obsessive compulsive disorder/ 50% superstition ;)