majic-ansible-roles Files · roles/backup

Files @ 3c03c2ea9d2a

Branch filter:

Location: majic-ansible-roles/roles/backup_client/defaults/main.yml - annotation

3c03c2ea9d2a 791 B text/x-yaml Show Source Show as Raw Download as Raw

branko

MAR-128: Upgraded tests for bootstrap role:

- Switch to new Molecule configuration.
- Updated set-up playbook to use become: yes.
- Moved some preparatory steps outside of the main playbook (eases
idempotence tests).
- Updated tests to reference the yml inventory file.
- Updated tests to use new fixture (host instead of individual ones).
- Fixed some linting issues.

a45dcc06530a
a45dcc06530a
d61d01c00362
3498d77cad32
19020779a000
d61d01c00362
bfafd526bfc3
bfafd526bfc3
bfafd526bfc3
bfafd526bfc3
bfafd526bfc3
bfafd526bfc3
bfafd526bfc3
bfafd526bfc3
bfafd526bfc3
bfafd526bfc3
279640b2178c
bfafd526bfc3
bfafd526bfc3
279640b2178c
bfafd526bfc3
bfafd526bfc3
bfafd526bfc3

---

backup_additional_encryption_keys: []
backup_client_username: "bak-{{ ansible_fqdn | replace('.', '_') }}"
backup_server_destination: /duplicity
backup_server_port: 2222

# Internal parameters.

# GnuPG 2 binary in Debian Jessie and Debian Stretch is different. Additionally,
# Debian Jessie duply configuration expects short keys, while Debian Stretch
# expects long keys. We set-up parameters for this here in a bit of a workaround
# way instead of setting facts within the playbook.
backup_client_gnupg_details:
  jessie:
    binary: gpg2
    cutoff: '8'
  stretch:
    binary: gpg
    cutoff: '0'

gnupg_binary: "{{ backup_client_gnupg_details[ansible_distribution_release]['binary'] }}"
gnupg_key_cutoff: "{{ backup_client_gnupg_details[ansible_distribution_release]['cutoff'] }}"