Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/sous-chefs/yum-epel
Development repository for the yum-epel cookbook
https://github.com/sous-chefs/yum-epel
chef chef-cookbook chef-resource hacktoberfest managed-by-terraform yum-epel
Last synced: about 1 month ago
JSON representation
Development repository for the yum-epel cookbook
- Host: GitHub
- URL: https://github.com/sous-chefs/yum-epel
- Owner: sous-chefs
- License: apache-2.0
- Created: 2013-12-06T03:56:24.000Z (about 11 years ago)
- Default Branch: main
- Last Pushed: 2024-02-01T00:28:00.000Z (11 months ago)
- Last Synced: 2024-04-14T06:09:21.461Z (8 months ago)
- Topics: chef, chef-cookbook, chef-resource, hacktoberfest, managed-by-terraform, yum-epel
- Language: Ruby
- Homepage: https://supermarket.chef.io/cookbooks/yum-epel
- Size: 305 KB
- Stars: 24
- Watchers: 24
- Forks: 75
- Open Issues: 3
-
Metadata Files:
- Readme: README.md
- Changelog: CHANGELOG.md
- Contributing: CONTRIBUTING.md
- License: LICENSE
- Code of conduct: CODE_OF_CONDUCT.md
- Codeowners: .github/CODEOWNERS
Awesome Lists containing this project
README
# yum-epel Cookbook
[](https://supermarket.chef.io/cookbooks/yum-epel)
[](https://github.com/sous-chefs/yum-epel/actions?query=workflow%3Aci)
[](#backers)
[](#sponsors)
[](https://opensource.org/licenses/Apache-2.0)
Extra Packages for Enterprise Linux (or EPEL) is a Fedora Special Interest Group that creates, maintains, and manages a high quality set of additional packages for Enterprise Linux, including, but not limited to, Red Hat Enterprise Linux (RHEL), CentOS , CentOS Stream and Scientific Linux (SL), Oracle Linux (OL).
The yum-epel cookbook takes over management of the default repositoryids shipped with epel-release.
Below is a table showing which repositoryids we manage that are shipped by default via the epel-release package:
| Repo ID | EL 7 | EL 8 | EL 9 | CentOS Stream 8 | CentOS Stream 9 |
| ------------------------------ | :--------------: | :--------------: | :--------------: | :--------------: | :--------------: |
| epel |:heavy_check_mark:|:heavy_check_mark:|:heavy_check_mark:|:heavy_check_mark:|:heavy_check_mark:|
| epel-debuginfo |:heavy_check_mark:|:heavy_check_mark:|:heavy_check_mark:|:heavy_check_mark:|:heavy_check_mark:|
| epel-next | :x: | :x: | :x: |:heavy_check_mark:|:heavy_check_mark:|
| epel-next-debuginfo | :x: | :x: | :x: |:heavy_check_mark:|:heavy_check_mark:|
| epel-next-source | :x: | :x: | :x: |:heavy_check_mark:|:heavy_check_mark:|
| epel-next-testing | :x: | :x: | :x: |:heavy_check_mark:|:heavy_check_mark:|
| epel-next-testing-debug | :x: | :x: | :x: |:heavy_check_mark:|:heavy_check_mark:|
| epel-next-testing-source | :x: | :x: | :x: |:heavy_check_mark:|:heavy_check_mark:|
| epel-source |:heavy_check_mark:|:heavy_check_mark:|:heavy_check_mark:|:heavy_check_mark:|:heavy_check_mark:|
| epel-testing |:heavy_check_mark:|:heavy_check_mark:|:heavy_check_mark:|:heavy_check_mark:|:heavy_check_mark:|
| epel-testing-debuginfo |:heavy_check_mark:|:heavy_check_mark:|:heavy_check_mark:|:heavy_check_mark:|:heavy_check_mark:|
| epel-testing-source |:heavy_check_mark:|:heavy_check_mark:|:heavy_check_mark:|:heavy_check_mark:|:heavy_check_mark:|
## Requirements
### Platforms
- RHEL/CentOS and derivatives
### Chef
- Chef 12.15+
## Maintainers
This cookbook is maintained by the Sous Chefs. The Sous Chefs are a community of Chef cookbook maintainers working together to maintain important cookbooks. If you’d like to know more please visit [sous-chefs.org](https://sous-chefs.org/) or come chat with us on the Chef Community Slack in [#sous-chefs](https://chefcommunity.slack.com/messages/C2V7B88SF).
### Cookbooks
- none
## Attributes
See individual repository attribute files for defaults.
## Recipes
- `yum-epel::default` Generates `yum_repository` configs for the standard EPEL repositories. By default the `epel` repository is enabled. For CentOS Stream, the [epel-next](https://docs.fedoraproject.org/en-US/epel/#what_is_epel_next) repository is also enabled.
## Usage Example
To disable the epel repository through a Role or Environment definition
```ruby
default_attributes(
:yum => {
:epel => {
:enabled => {
false
}
}
}
)
```
Uncommonly used repositoryids are not managed by default. This is speeds up integration testing pipelines by avoiding yum-cache builds that nobody cares about. To enable the epel-testing repository with a wrapper cookbook, place the following in a recipe:
```ruby
node.default['yum']['epel-testing']['enabled'] = true
node.default['yum']['epel-testing']['managed'] = true
include_recipe 'yum-epel'
```
## More Examples
Point the epel repositories at an internally hosted server.
```ruby
node.default['yum']['epel']['enabled'] = true
node.default['yum']['epel']['mirrorlist'] = nil
node.default['yum']['epel']['baseurl'] = 'https://internal.example.com/centos/7/os/x86_64'
node.default['yum']['epel']['sslverify'] = false
include_recipe 'yum-epel'
```
## Contributors
This project exists thanks to all the people who [contribute.](https://opencollective.com/sous-chefs/contributors.svg?width=890&button=false)
### Backers
Thank you to all our backers!
### Sponsors
Support this project by becoming a sponsor. Your logo will show up here with a link to your website.
