Installing MariaDB .deb Files with Ansible

This page refers to the operations described in Installing MariaDB .deb Files. Refer to that page for a complete list and explanation of the tasks that should be performed.

Here we discuss how to automate such tasks using Ansible. For example, here we show how to install a package or how to import a GPG key; but for an updated list of the necessary packages and for the keyserver to use, you should refer to Installing MariaDB .deb Files.

Adding apt Repositories

To add a repository:

If you prefer to keep the repository information in a source list file in the Ansible repository, you can upload that file to the target hosts in this way:

Updating the Repository Cache

Both the Ansible modules and have an update_cache attribute. In ansible.builtin.apt it is set to "no" by default. Whenever a task sets it to 'yes', apt-get update is run on the target system. You have three ways to make sure that repositories are updated.

The first is to use ansible.builtin.apt_repository to add the desired repository, as shown above. So you only need to worry about updating repositories if you use the file method.

The second is to make sure that update_cache is set to 'yes' when you install a repository:

But if you run certain tasks conditionally, this option may not be very convenient. So the third option is to update the repository cache explicitly as a separate task:

Importing MariaDB GPG Key

To for MariaDB we can use the Ansible module. For example:

Installing Packages

To install Deb packages into a system:

To make sure that a specific version is installed, performing an upgrade or a downgrade if necessary:

To install a package or upgrade it to the latest version, use: state: latest.

To install multiple packages at once:

If all your servers run on the same system, you will always use ansible.builtin.apt and the names and versions of the packages will be the same for all servers. But suppose you have some servers running systems from the Debian family, and others running systems from the Red Hat family. In this case, you may find convenient to use two different task files for two different types of systems. To include the proper file for the target host's system:

The variables you can use to run the tasks related to the proper system are:

There is also a system-independent , but if the package names depend on the target system using it may be of very little benefit.

See Also

Content initially contributed by .

_{This page is licensed: CC BY-SA / Gnu FDL}