update

updates target systems using targets package manager, for example apt update.

Based on the fine role created by Robert de Bock with some minor modification added.

Install updates on your system.

Example Playbook

This example is taken from molecule/resources/playbook.yml:

---
- name: Converge
  hosts: all
  become: yes
  gather_facts: yes

  roles:
    - cjsteel.update

The machine you are running this on, may need to be prepared.

---
- name: Prepare
  hosts: all
  become: yes
  gather_facts: no

  roles:
    - role: cjsteel.bootstrap
      vars:
        - update_reboot: yes

Also see a full explanation and example on how to use these roles.

Role Variables

These variables are set in defaults/main.yml:

---
# defaults file for update

# For APT (Debian/Ubuntu) only: remove unused dependency packages for all module states except `build-dep'
update_autoremove: no

# For APT (Debian/Ubuntu) only: apt_upgrade type which can be: dist, full, yes, or safe
update_upgrade_command: dist

# For APT (Debian/Ubuntu) only: update the apt cache if it's older than the cache_valid_time.  Set in seconds.
update_cache_valid_time: 1

# When updating systems, a reboot may be required. Here you can select to:
# "yes": Always reboot when packages have changed.
# "no": Never reboot when packages have changed.
update_reboot: no

Requirements

• Access to a repository containing packages, likely on the internet.
• A recent version of Ansible. (Tests run on the current, previous and next release of Ansible.)

The following roles can be installed to ensure all requirements are met, using ansible-galaxy install -r requirements.yml:

---
- cjsteel.bootstrap
- cjsteel.reboot

Context

The original version of this role is a part of many compatible roles. Have a look at the documentation of these roles for further information.

Compatibility

The original version of the role has been tested against the following distributions and Ansible version:

A single star means the build may fail, it's marked as an experimental build.

Testing

This role

• Ubuntu bionic

If you find issues, please register them in GitHub

To test this role locally please use Molecule:

pip install molecule
molecule test

To test on Amazon EC2, configure ~/.aws/credentials and set a region using export AWS_REGION=eu-central-1 before running molecule test --scenario-name ec2.

There are many specific scenarios available, please have a look in the molecule/ directory.

Original roles testing

Unit tests are done on every commit and periodically.

License

Apache-2.0

Author Information

Robert de Bock