From 91b773e12e4de07244efb6bfcfde53d1573d1e54 Mon Sep 17 00:00:00 2001
From: Julien Dessaux
Date: Tue, 16 Feb 2021 15:11:40 +0100
Subject: Added action plugins to simplify borg role

---
 README | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

(limited to 'README')

diff --git a/README b/README
index 98d7b5b..32b392d 100644
--- a/README
+++ b/README
@@ -1,5 +1,4 @@
 There are several variables you can define to configure a machines response to the borg role :
-- is_borg_server: a boolean that indicates if a machine will act as a borg server
 - borg_server: a string that contains a borg servers hostname
 - borg_jobs: a list of dict, one item per job with the following keys:
   - name: the name of the borg job
@@ -14,3 +13,5 @@ Here are some job examples :
 - { name: etc, path: "/etc" }
 - { name: mysqldump, command_to_pipe: "/usr/bin/mysqldump -h {{ mysql_server }} -u{{ ansible_hostname }} -p{{ ansible_local.mysql_client.password }} --single-transaction --add-drop-database -B {{ ansible_hostname }}" }
 - { name: gitea, path: "/tmp/gitea.zip", pre_command: "echo '/usr/local/sbin/gitea -C /etc/gitea -c /etc/gitea/app.ini dump -f /tmp/gitea.zip' | su -l _gitea", post_command: "rm -f /tmp/gitea.zip" }
+
+There is an action plugin that parses the borg_server entries from all hosts and set a flag to True in adyxax['is_borg_server'] for any machine specified as a backup target
-- 
cgit v1.2.3