On Fri, May 26, 2023 at 04:28:56PM +0200, seddik alaoui ismaili wrote: > Hi folks, > > We decided to add cron to compress some merged logs. So I realize that we > didn't have any Ansible role to do this. > Currently we manage cron tasks separately in the component's role, and IMO > it will be difficult to find/make modifications when needed. > > Do you think it's beneficial to create new one ? Or perhaps someone has > clever ideas :) ? > > +1/-1 ?? I'm not sure cron is big enough to make a role worthwhile. You mean make a role that takes file/template name, when to run and puts it in /etc/cron.d/ ? We do have the ansible 'cron' module, which can do /etc/cron.d/ files as well, but of course still needs copying the template/file script first before it can be scheduled. So, I could be convinced, but I don't think it's worth it off hand... Happy to hear other/more thoughts on it tho, and thanks for bringing up the idea. It's nice when we can consolidate things into less duplication. :) kevin
Attachment:
signature.asc
Description: PGP signature
_______________________________________________ infrastructure mailing list -- infrastructure@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to infrastructure-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
