Docker module shouldn't manage the EPEL repository (via the epel module)

[tgm4883]

This is specifically an issue on RHEL/CentOS < 7 (Specifically, this code )

Use cases:

1. A user uses another module to manage the EPEL repository that conflicts with the module that puppetlabs-docker requires. (As discussed in this thread, where the developer states "have whatever is requiring a specific epel module to stop that."
2. A user uses yumrepo to manage EPEL rather than a module (which is what we do because we have a local copy of all the repositories we use)

Possible fix:

Add a class variable such as 'manage_epel' that can be set to false for users where EPEL is already being managed though some other means.

[scotty-c]

We will add this into our next sprint or if you have code already written we are also accepting PR's

[tgm4883]

Thanks scotty-c, I don't have code written.

[LongLiveCHIEF]

I already have code written for this, but it's only compatible hiera v5. What is this module's intent in terms of supporting EoL versions of puppet/hiera?

[scotty-c]

@LongLiveCHIEF This module will only support the versions we do at Puppet. So puppet 4 and above.
We will still need to support Hiera 3 as most customers have not moved to 5 yet

[scotty-c]

This will be fixed in PR #31

[scotty-c]

PR #31 is now in master, we have some other changes we would like to add before the next release.
So it will be published on the Forge with that release.

That release will be next week sometime