Install Google Chrome on Red Hat Using Ansible — Video Tutorial

How to Install Google Chrome in RedHat-like systems with Ansible? I'm going to show you a live Playbook with some simple Ansible code. I'm Luca Berton and welcome to today's episode of Ansible Pilot. Ansible install Google Chrome in RedHat-like systems - Add Google Chrome key => ansible.builtin.rpm_key - Add Google Chrome repository => ansible.builtin.yum_repository - Update yum cache and install Google Chrome => ansible.builtin.yum In order to install Google Chrome on a RedHat-like system, we need to perform three different steps. The first step is to download the GPG signature key for the repository. You are going to use the `ansible.builtin.rpm_key` Ansible module. This encrypted key verifies the genuinity of the packages and the repository and guarantees that the software is the same as Google releases. The second step is to add the add Google Chrome repository to the distribution. It’s an extra website where `yum/dnf`, your distribution package manager looks like for software. You are going to use the `ansible.builtin.yum_repository` Ansible module. The third step is to update the yum cache for the available packages and install Google Chrome using the `ansible.builtin.yum` Ansible module. Parameters - `rpm_key` `key` string — URL - `rpm_key` `state` string — present/absent - `yum_repository` `name` string — repository - `yum_repository` `baseurl` string — URL - `yum_repository` `gpgcheck` boolean — enable GPG - `yum_repository` `gpgkey` string — GPG check and key URL - `yum` `name` string — name or package-specific - `yum` `state` string — latest/present/absent - `yum` `update_cache` boolean — no/yes For the `ansible.builtin.rpm_key` Ansible module I’m going to use two parameters: `“key”` and `“state”`. The “key” parameter specifies the URL or the key ID of the repository gpg signature key and the “state” verify that is present in our system after the execution. For the `ansible.builtin.yum_repository` Ansible module I’m going to use four parameters: `“name”`, `“baseurl”`, `“gpgcheck”` and `“gpgkey”`. The “name” parameter specifies the repository parameters and the `“baseurl”` URL of it. The `“gpgcheck”` parameter enables the gpg verification with the URL specified in `“gpgkey”` parameter. For the `ansible.builtin.yum` Ansible module I’m going to use three parameters: “name”, “state”, and “update_cache”. The “name” parameter specifies the package name (Google Chrome in our use-case) and the “state” verify that is present in our system after the execution. Before installing the package the “update_cache” performs an update of the yum cache to ensure that the latest version of the package is going to be downloaded. ## Playbook Install Google Chrome in RedHat-like systems with Ansible Playbook. code - install_chrome_redhat.yml ```yaml --- - name: install Google Chrome hosts: all become: true tasks: - name: Add Yum signing key ansible.builtin.rpm_key: key: https://dl.google.com/linux/linux_signing_key.pub