ansible-personal/roles/common/tasks/tarsnap.yml

---
- name: Add Tarsnap apt mirror
  template: src=tarsnap_sources.list.j2 dest=/etc/apt/sources.list.d/tarsnap.list owner=root group=root mode=0644
  register: add_tarsnap_apt_repository
  when: ansible_architecture != 'armv7l'

- name: Add GPG key for Tarsnap
  apt_key: id=0x6D97F5A4CA38CF33 url=https://pkg.tarsnap.com/tarsnap-deb-packaging-key.asc state=present
  when: ansible_distribution_release != 'buster'
  register: add_tarsnap_apt_key

# Tarsnap currently provides experimental packages for Debian 10 "buster"
# See: https://www.tarsnap.com/pkg-deb.html#experimental
- name: Add GPG key for Tarsnap experimental
  apt_key: id=0xF77F1024ECFAF293 url=https://pkg.tarsnap.com/experimental/tarsnap-EXPERIMENTAL-deb-packaging-key.asc state=present
  when: ansible_distribution == 'Debian' and ansible_distribution_release == 'buster'
  register: add_tarsnap_apt_key

- name: Update apt cache
  apt:
    update_cache: yes
  when:
    add_tarsnap_apt_key is changed or
    add_tarsnap_apt_repository is changed

- name: Install tarsnap
  apt: pkg=tarsnap cache_valid_time=3600

- name: Copy tarsnaprc
  copy: src=tarsnaprc dest=/root/.tarsnaprc owner=root group=root mode=0600

# vim: set sw=2 ts=2:
roles/common: Add tasks to install tarsnap Now that Tarsnap has official packages this is one less thing that needs to be manually installed from source after bringing a machine up. See: http://mail.tarsnap.com/tarsnap-announce/msg00037.html 2017-02-07 16:28:35 +01:00			`---`
			`- name: Add Tarsnap apt mirror`
			`template: src=tarsnap_sources.list.j2 dest=/etc/apt/sources.list.d/tarsnap.list owner=root group=root mode=0644`
Smarter updating of apt index during playbook execution We can register changes when adding repositories and keys and then update the apt package index conditionally. This should make it be more consistent between initial host setup and subsequent re-runs. 2019-03-17 16:29:15 +01:00			`register: add_tarsnap_apt_repository`
roles/common: Add tasks to install tarsnap Now that Tarsnap has official packages this is one less thing that needs to be manually installed from source after bringing a machine up. See: http://mail.tarsnap.com/tarsnap-announce/msg00037.html 2017-02-07 16:28:35 +01:00			`when: ansible_architecture != 'armv7l'`

			`- name: Add GPG key for Tarsnap`
roles/common: Fix tarsnap package key For some reason the key ID I had here was wrong. According to the Tarsnap website the key ID is 0x6D97F5A4CA38CF33. ee: https://www.tarsnap.com/pkg-deb.html 2019-07-07 14:49:45 +02:00			`apt_key: id=0x6D97F5A4CA38CF33 url=https://pkg.tarsnap.com/tarsnap-deb-packaging-key.asc state=present`
roles/common: Use experimental Tarsnap on Debian buster Tarsnap currently provides experimental packages for Debian Buster. See: https://www.tarsnap.com/pkg-deb.html#experimental 2019-07-19 11:07:27 +02:00			`when: ansible_distribution_release != 'buster'`
			`register: add_tarsnap_apt_key`

			`# Tarsnap currently provides experimental packages for Debian 10 "buster"`
			`# See: https://www.tarsnap.com/pkg-deb.html#experimental`
			`- name: Add GPG key for Tarsnap experimental`
			`apt_key: id=0xF77F1024ECFAF293 url=https://pkg.tarsnap.com/experimental/tarsnap-EXPERIMENTAL-deb-packaging-key.asc state=present`
			`when: ansible_distribution == 'Debian' and ansible_distribution_release == 'buster'`
Smarter updating of apt index during playbook execution We can register changes when adding repositories and keys and then update the apt package index conditionally. This should make it be more consistent between initial host setup and subsequent re-runs. 2019-03-17 16:29:15 +01:00			`register: add_tarsnap_apt_key`
roles/common: Add tasks to install tarsnap Now that Tarsnap has official packages this is one less thing that needs to be manually installed from source after bringing a machine up. See: http://mail.tarsnap.com/tarsnap-announce/msg00037.html 2017-02-07 16:28:35 +01:00
Smarter updating of apt index during playbook execution We can register changes when adding repositories and keys and then update the apt package index conditionally. This should make it be more consistent between initial host setup and subsequent re-runs. 2019-03-17 16:29:15 +01:00			`- name: Update apt cache`
			`apt:`
			`update_cache: yes`
			`when:`
			`add_tarsnap_apt_key is changed or`
			`add_tarsnap_apt_repository is changed`

roles/common: Add tasks to install tarsnap Now that Tarsnap has official packages this is one less thing that needs to be manually installed from source after bringing a machine up. See: http://mail.tarsnap.com/tarsnap-announce/msg00037.html 2017-02-07 16:28:35 +01:00			`- name: Install tarsnap`
roles: The apt cache_valid_time implies update_cache See: https://docs.ansible.com/ansible/latest/modules/apt_module.html 2019-03-17 16:29:28 +01:00			`apt: pkg=tarsnap cache_valid_time=3600`
roles/common: Add tasks to install tarsnap Now that Tarsnap has official packages this is one less thing that needs to be manually installed from source after bringing a machine up. See: http://mail.tarsnap.com/tarsnap-announce/msg00037.html 2017-02-07 16:28:35 +01:00
roles/common: Add task to copy tarsnaprc One less thing to do manually after server provisioning, and there is nothing sensitive in here anyways. 2018-05-20 11:51:02 +02:00			`- name: Copy tarsnaprc`
			`copy: src=tarsnaprc dest=/root/.tarsnaprc owner=root group=root mode=0600`

roles/common: Add tasks to install tarsnap Now that Tarsnap has official packages this is one less thing that needs to be manually installed from source after bringing a machine up. See: http://mail.tarsnap.com/tarsnap-announce/msg00037.html 2017-02-07 16:28:35 +01:00			`# vim: set sw=2 ts=2:`