Allow cron to update existing cron entries
Nobody has claimed this yet.
- Dominant language
- Perl
- Stars
- 737
- Forks
- 214
- PR merge metrics
- No merged PRs in 30d
Description
To change a cron entry, it first needs to be marked absent, changed, and then re-run.
What Ansible and Puppet do is prepend a comment that they use to identify the cron job by resource name, so that changes can be updated.
Perhaps the way to implement this is to provide an optional "update" (boolean) argument to cron_entry (or cron_add). If the update argument is true, then it looks for a line with "Rex: " + resource name rather than the exact cron job.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the cron_entry and cron_add entry points mentioned in the issue, then inspect how existing cron entries are identified and how absent entries are handled. Compare the requested resource-name comment approach with the current behavior. Done means an optional update mode can find and change an existing entry by resource name without requiring a separate absent step.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- perl
- Domain
- devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100