Install Microsoft Edge in RedHat-like systems - Ansible module rpm_key, yum_repository and yum — Video Tutorial

How to Install Microsoft Edge 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. Microsoft Edge on Linux Microsoft Edge is available in the following channels: - Stable Channel - Beta Channel - Major update every 4 weeks - Dev Channel - Updated weekly - Canary Channel - Updated daily More information https://www.microsoftedgeinsider.com/en-us/download/ Ansible install Microsoft Edge in RedHat-like systems - Add Microsoft Edge key => ansible.builtin.rpm_key - Add Microsoft Edge repository => ansible.builtin.yum_repository - Update yum cache and install Microsoft Edge => ansible.builtin.yum In order to install Microsoft Edge 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 Microsoft releases. The second step is to add the add Microsoft Edge 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 Microsoft Edge 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 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 (Microsoft Edge 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 apt cache to ensure that the latest version of the package is going to be downloaded. ## Playbook Let's jump in a real-life Ansible Playbook to install Microsoft Edge in RedHat-like systems. code - in