Restore cronjob playbook #87

Closed
opened 2021-07-14 13:39:35 +02:00 by muppeth · 1 comment
Owner

Since a while cronjob playbook is not running automatically. To fix this we should update host_vars to make sure no cronjob is missing as it will get overwritten.
Things to do:

  • Check all host_vars to see which ones have crontab setup
  • Check if cronjobs from those hosts arent missing or are different on prod
  • Update host_vars
  • Create PR
  • Merge PR
  • Setup crontab on operations
  • ...
  • profit!
Since a while cronjob playbook is not running automatically. To fix this we should update host_vars to make sure no cronjob is missing as it will get overwritten. Things to do: - [x] Check all host_vars to see which ones have crontab setup - [x] Check if cronjobs from those hosts arent missing or are different on prod - [x] Update host_vars - [x] Create PR - [ ] Merge PR - [ ] Setup crontab on operations - [ ] ... - [ ] profit!
muppeth added the
enhancement
label 2021-07-14 13:39:35 +02:00
Owner

The PR is created on host_vars

The PR is created on host_vars
Sign in to join this conversation.
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: Disroot/Disroot-Project#87
No description provided.