Backups are currently handled by a pretty fragile script. Plan it to set up a more robust backup plan using restic and use a systemd timer to run it automatically.
Context
Backups are required for any proper setup. Without them data lose is bound to happen. Having a proper backup plan in place will help mitigate the risk of data loss in the event of hardware failure, user error or malicious actions
Proposed Changes
New backup role that does the following
install restic on the target
install rclone on the target
create rclone.config and require remote
creates systemd timer that runs as root to run the backup
Verification Plan
Verification of this will be done by running the playbook with the new role against a test environment. This will verify the playbook itself is working correctly
Once the playbook is confirmed working, a test of the backup itself will be ran by manually trigger the service with systemd to verify end to end.
### Summary
Backups are currently handled by a pretty fragile script. Plan it to set up a more robust backup plan using restic and use a systemd timer to run it automatically.
### Context
Backups are required for any proper setup. Without them data lose is bound to happen. Having a proper backup plan in place will help mitigate the risk of data loss in the event of hardware failure, user error or malicious actions
### Proposed Changes
- [x] New backup role that does the following
- [x] install restic on the target
- [x] install rclone on the target
- [x] create rclone.config and require remote
- [x] creates systemd timer that runs as root to run the backup
### Verification Plan
Verification of this will be done by running the playbook with the new role against a test environment. This will verify the playbook itself is working correctly
Once the playbook is confirmed working, a test of the backup itself will be ran by manually trigger the service with systemd to verify end to end.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Summary
Backups are currently handled by a pretty fragile script. Plan it to set up a more robust backup plan using restic and use a systemd timer to run it automatically.
Context
Backups are required for any proper setup. Without them data lose is bound to happen. Having a proper backup plan in place will help mitigate the risk of data loss in the event of hardware failure, user error or malicious actions
Proposed Changes
Verification Plan
Verification of this will be done by running the playbook with the new role against a test environment. This will verify the playbook itself is working correctly
Once the playbook is confirmed working, a test of the backup itself will be ran by manually trigger the service with systemd to verify end to end.