Ecosyste.ms: Awesome

An open API service indexing awesome lists of open source software.

Awesome Lists | Featured Topics | Projects

https://github.com/juju4/ansible-redhat-epel

A simple ansible role to setup Redhat EPEL
https://github.com/juju4/ansible-redhat-epel

Last synced: 2 months ago
JSON representation

A simple ansible role to setup Redhat EPEL

Awesome Lists containing this project

README

        

[![Actions Status - Master](https://github.com/juju4/ansible-redhat-epel/workflows/AnsibleCI/badge.svg)](https://github.com/juju4/ansible-redhat-epel/actions?query=branch%3Amaster)
[![Actions Status - Devel](https://github.com/juju4/ansible-redhat-epel/workflows/AnsibleCI/badge.svg?branch=devel)](https://github.com/juju4/ansible-redhat-epel/actions?query=branch%3Adevel)

# RedHat EPEL ansible role

A simple ansible role to setup Redhat EPEL
* http://fedoraproject.org/wiki/EPEL
* https://docs.fedoraproject.org/en-US/epel/

## Requirements & Dependencies

### Ansible
It was tested on the following versions:
* 1.9
* 2.0
* 2.2

### Operating systems

Tested with Centos 7 and 8

## Example Playbook

Just include this role in your list.
For example

```
- host: all
roles:
- juju4.redhat-epel
```

## Variables

Nothing specific for now.

## Continuous integration

This role has a travis basic test (for github), more advanced with kitchen and also a Vagrantfile (test/vagrant).
Default kitchen config (.kitchen.yml) is lxd-based, while (.kitchen.vagrant.yml) is vagrant/virtualbox based.

Once you ensured all necessary roles are present, You can test with:
```
$ cd /path/to/roles/juju4.redhat-epel
$ kitchen verify
$ kitchen login
$ KITCHEN_YAML=".kitchen.vagrant.yml" kitchen verify
```
or
```
$ cd /path/to/roles/juju4.redhat-epel/test/vagrant
$ vagrant up
$ vagrant ssh
```

## Troubleshooting & Known issues

* While EPEL for RedHat/Centos 6 is still included, it is EOL and it is strongly recommended to upgrade to recent release.

## License

BSD 2-clause