ptfs-europe / koha-plugin-crontab Goto Github PK

We should formalise a specification for metadata that can be added to cron "blocks" so that ansible/system maintained crontab files and plugin maintained cron config can interact more cleanly.

I'm thinking things like marking cronjobs as 'system/readonly', 'hidden', 'user ownership' etc

Hi,
It would be awesome to allow only specified users to access this plugin, either through koha-conf configuration or Superlibrarian only access to the configs for this plugin.

For example, Tools->plugins permission might be too permissive, we might want to only allow support staff to access this account, or only a very few designated people at the library.

Low priority just wanted to document the idea:

The environment variables could be confusing to see all the time, it might be good to collapse them during normal usage (i.e. I came to this page to see the defined crons, not half a page of environment variables)

Would it make sense to be able to run this in two different moeds, one where you can only view the crons, and one where you can edit them too?

It could be a on/off switch somwhere like koha-conf.xml, or somehow configured differently for different users, so perhaps superlibrarians could edit and others could view? Or even more fine grained, with settings for individual users.

Related to #2, probably.

I think it's a good idea for this to live under the administration pages as opposed to under tools.. as such I've submitted "Bug 36206 - Administrative plugins" to Koha and there's a corresponding admin_plugin branch here.

Add the ability to log changes to the koha user's cron to the Koha action_logs, including diff.

When you define a file in koha-conf.xml, if # Block: 0 is not existent, the environment will not save. Adding this into the koha-conf.xml defined file allows the environment to be saved correctly.

We closed issue #2 with an option to limit users to a config file-driven allow list. I'd still, however, like to add the option to control users using the core user permissions system and I'm working on bugs in core to allow for this.

We currently default to the koha-shell users crontab. Some systems instead use a cron.d/koha-instance file and we should be able to use that instead... or any other location for that matter so long as the koha-instance user has read/write access appropriately

For example, we might want to restrict users to only scheduling reports. I'm thinking a dropdown or other interface that adds all of the necessary path and job information, and shows the usage for that job.

runreport.pl is the first one I thought of and a good one to proof of concept.