https://docs.ansible.com/ansible-tower/3.2.4/html_ja/installandreference/_static/images/logo_invert.png" width="10%" height="10%" alt="Ansible logo" align="right"/>
Install updates on your system.
This example is taken from molecule/resources/playbook.yml
:
--- - name: Converge hosts: all become: yes gather_facts: yes roles: - haghighi_ahmad.update
The machine you are running this on, may need to be prepared.
--- - name: Prepare hosts: all become: yes gather_facts: no roles: - haghighi_ahmad.bootstrap
Also see a full explanation and example on how to use these roles.
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: yes
The following roles can be installed to ensure all requirements are met, using ansible-galaxy install -r requirements.yml
:
--- - haghighi_ahmad.bootstrap - haghighi_ahmad.reboot
This role has been tested against the following distributions and Ansible version:
distribution | ansible 2.7 | ansible 2.8 | ansible devel |
---|---|---|---|
alpine-edge* | yes | yes | yes* |
alpine-latest | yes | yes | yes* |
archlinux | yes | yes | yes* |
centos-6 | yes | yes | yes* |
centos-latest | yes | yes | yes* |
debian-stable | yes | yes | yes* |
debian-unstable* | yes | yes | yes* |
fedora-latest | yes | yes | yes* |
fedora-rawhide* | yes | yes | yes* |
opensuse-leap | yes | yes | yes* |
ubuntu-devel* | yes | yes | yes* |
ubuntu-latest | yes | yes | yes* |
ubuntu-rolling | yes | yes | yes* |
A single star means the build may fail, it's marked as an experimental build.
Unit tests are done on every commit and periodically.
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.
Apache-2.0