...
If you are upgrading from a version previous to 3.5.0 or greater, please read: Upgrading Opmantek Applications
opConfig 3.5.1
RELEASED 29 30 Oct 2020
- Bugfix: When a command throws an error - For example, opConfig has no access to the node anymore - The last revision information was lost. It still persists in the database, in the collection command_output_log. But in the GUI, the revision is shown as no data. The behaviour was modified:
- If there is an error with the command, a new revision is saved, indicating the last attempt and the error, even if no text output is received.
- If the new revision has the same result as the previous, the information will be assigned to revision 0. This is the same behaviour, but now also happens with revisions with error.
- Purging rules: The command purge_revisions has been modified. Now, it also removes a queue when a revision is removed, if there are not other existing jobs referencing another existing revision. Also, a new command was created, purge_queue, to remove old jobs not linked with any revision, based in the parameter
opconfig_queue_expire_after_seconds
This parameter is 8 days by default, and is specified in seconds. You can read more about the purging data in opConfig in the next link. - List queue: Now it returns only the pending jobs by default. All the jobs can be listed with all=1.
...