Releases: XactSystems/command-scheduler
Wrap the command completion code in a transaction.
Wrap the command completion code in a transaction
Add Data and RunAt columns
Merge in changes from 3.4.
Tidy up multiple factory classes into one.
Use the same names for history methods as the DB fields, add Last prefix.
Fix cascade option in OneToMany.
Use the correct ManagerRegistry class in the repository.
Display blank for null runAt and lastRunAt values in the list.
Add RunAt to the scheduled command list.
Add RunAt to the scheduled command list. Use a fluid container.
Add Data and RunAt columns
Add the ability to store string data with the command. This can be used to serialise an object for use within the command.
Add the --command-id option to the fixed parameters on the run command, this passes the id of the ScheduledCommand entity.
Add the RunAt field to the ScheduledCommand entity to allow for running commands once at a specific date and time.
Bug fix
Save error output
Add LastError to the entities, display output and error incrementally if verbose, remove arguments from the command index view.
This is another BC break! LastError needs adding to both the ScheduledCommand and ScheduledCommandHistory tables.
Use Symfony Process component to run commands.
Abandoned trying to get the commands running via the console application. It was getting very complex trying to get arguments parsed on both Linux and Windows.
This has required a BC break to include a Status field in the entity and requires setting to PENDING for all current commands.
Use Winbox/Args to escape command arguments.
Merge pull request #2 from XactSystems/3.4.x Use Winbox/Args to escape command arguments.
Use an array for command arguments
Use an array instead of a string for command arguments.
N.B. This is a BC break for command arguments provided to ScheduledCommand and the CommandSchedulerFactory methods.
Add command factory
Create a factory class and rename the internal history factory class.