Remote backups? Honestly haven't had time to attack. I'll bump the priority though so it doesn't get lost in the shuffle -- it's a good idea -- and an OLD idea :)
On Thu, Jul 31, 2014 at 4:09 PM, Mike Ray <[email protected]> wrote: > What is the status of this? My team would find a feature like this > immensely helpful. > > It would be additionally useful if you could force it to only maintain X > backups in said backup directory. > > I see nothing in the changelogs about this. > > > On Saturday, October 12, 2013 12:44:52 PM UTC-5, Vadim Shkolin wrote: >> >> I made the pull request (username: vshkolin) >> >> суббота, 12 октября 2013 г., 4:24:07 UTC+4 пользователь Michael DeHaan >> написал: >>> >>> I would be interested in seeing and commenting on the pull request. >>> >>> We can see what it looks like and go from there. >>> >>> Thanks! >>> >>> >>> On Fri, Oct 11, 2013 at 7:15 PM, Vadim Shkolin <[email protected]> >>> wrote: >>> >>>> I think, that mostly all ansible users work as root - native or over >>>> sudo. OK, path for backups can be changed. >>>> >>>> This is not "if this were implemented". This is implemented by me :). >>>> >>>> Old (native) backup's mechanism is unusable: >>>> 1. It has potential conflict with "conf.d"-like distros >>>> 2. There is data overriding when file is modified twice in one >>>> playbook, for example, many "lineinfile" step-by-step. The first >>>> modification will make backup with pattern %Y-%m-%d@%H:%M~, and the >>>> second one will override this backup. Original file will lost, it is a BIG >>>> problem for production systems! >>>> I changed the pattern to %Y%m%d-%H%M%S, and added version number suffix >>>> to it, if this file still exists (if step-by-step modifications will be in >>>> same second). >>>> >>>> I can push this modification into new git branch, and you can check and >>>> modify it (add homedir in backup path, etc.), and merge into devel branch. >>>> >>>> суббота, 12 октября 2013 г., 1:10:19 UTC+4 пользователь James Cammarata >>>> написал: >>>>> >>>>> Since tasks are run as potentially different users (none of which may >>>>> have root access), creating a common directory for backups may not work. >>>>> Most likely, if this were implemented, the backup directory would have to >>>>> be under the user's home directory by default. >>>>> >>>>> >>>>> On Fri, Oct 11, 2013 at 3:41 PM, Vadim Shkolin <[email protected]> >>>>> wrote: >>>>> >>>>>> File modules of ansible ("copy", module and some others) can do >>>>>> backup of changed data. The standard naiming schema (timestamping and >>>>>> adding '~' in original directory) can have bad effects in "conf.d"-like >>>>>> distros. >>>>>> >>>>>> Main idea: all backups placed into separate directory tree, based on >>>>>> /var/lib/ansible.backups. 1st backup is suffixed by '.orig', 2nd and more >>>>>> later are suffixed by timestamp. This schema is more reliable, and I made >>>>>> patch for it. >>>>>> >>>>>> New schema example: >>>>>> >>>>>> /var/lib/ansible.backups/etc/zabbix >>>>>> /var/lib/ansible.backups/etc/zabbix/zabbix_agentd.conf. >>>>>> 20130622-172930 >>>>>> /var/lib/ansible.backups/etc/zabbix/zabbix_proxy.conf. >>>>>> 20130622-172959 >>>>>> /var/lib/ansible.backups/etc/zabbix/zabbix_proxy.conf.orig >>>>>> /var/lib/ansible.backups/etc/zabbix/zabbix_agentd.conf. >>>>>> 20130614-033941 >>>>>> /var/lib/ansible.backups/etc/zabbix/zabbix_agentd.conf.orig >>>>>> >>>>>> Do you interested it? If so, how can I commit this changes into main >>>>>> tree? >>>>>> -- >>>>>> 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]. >>>>>> >>>>>> For more options, visit https://groups.google.com/groups/opt_out. >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> >>>>> James Cammarata <[email protected]> >>>>> >>>>> Sr. Software Engineer, AnsibleWorks, Inc. >>>>> http://www.ansibleworks.com/ >>>>> >>>> -- >>>> 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]. >>>> For more options, visit https://groups.google.com/groups/opt_out. >>>> >>> >>> >>> >>> -- >>> Michael DeHaan <[email protected]> >>> CTO, AnsibleWorks, Inc. >>> http://www.ansibleworks.com/ >>> >>> -- > 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/7656a5b6-b992-45e2-a151-8dfdb09dbc7c%40googlegroups.com > <https://groups.google.com/d/msgid/ansible-project/7656a5b6-b992-45e2-a151-8dfdb09dbc7c%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- 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/CA%2BnsWgzhFMbGyOaJ4oo9sHmvF13Lhg0s4GqiTeFtKxMdxa2uOw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
