On Wednesday, May 28, 2014 6:58:55 AM UTC-5, Michael DeHaan wrote:
>
>
> Otherwise you are backing up only the things that ansible has known it
> changed, which doesn't include things that the software could have changed
> by itself (databases) or users logging in.
>
Right -- that's assuming the scope of the backup role. Simply; the backup
role sets up a consistent backup mechanism and what paths to back up; and
roles can tap into this to *augment* what gets backed up as well. It
primarily does this by managing an rsync include file; but uses
line_in_file vs templating/copying to ensure that outside ("software"?)
changes don't get overwritten.
In any case the intralinked site/backup role was just an example of a
situation I had where one role needed to use a variable from another role;
and I opened this thread to get an idea on how to best do so.
Thanks as always for the chastisement. Fear not, man ... I won't venture
into the empire of Atilla DeHaan unless necessary bugs creep up ;)
--
You received this message because you are subscribed to the Google Groups
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/ansible-project/0a7d3cc6-8fd4-4188-a688-dcd776f3ba7d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
