target parameter not applying

[dgkrieger]

Affected Puppet, Ruby, OS and module versions/distributions

• Puppet: Open 4.10 (puppetserver 2.7.2)
• Ruby: 2.0.0p648
• Distribution: Oracle Linux 7.3
• Module version: 2.0.0

How to reproduce (e.g Puppet code you use)

builtin epel repository

What are you seeing

epel repository file gets written as:
/etc/yum.repos.d/Extra Packages for Enterprise Linux 7 - $basearch - Debug.repo

What behaviour did you expect instead

expected /etc/yum.repos.d/epel-debuginfo.repo

I expected the target parameter to control the file name based on the yumrepo resource type. I have seen that this is a previous know issue. Are there any recommendations to work around this? The only one I have is to remove the name parameter so that it takes the name of the resource.

Output log

Any additional information you'd like to impart

[dgkrieger]

It is possible to change the name parameter in the repos.yaml to descr. This this has the file name and repo contents populated correctly.

[pvdmarel]

With the 2.1.0 version of this module the target parameter is still not used. Is there another way to assign the file-name, and preferably combine multiple repos into one file? (Using RHEL 7.4 with the latest puppetserver open source version (5.1.4))

[joekohlsdorf]

This looks like an issue in the puppet yumrepo resource type. I took a quick glance at the code and it looks like the variable target never gets referenced in the provider.
The puppet-yum module itself passes all parameters unmodified to yumrepo and isn't at fault here.

The bug should be verified and reported against puppetlabs/puppet.

[jorhett]

It has been for some time: https://tickets.puppetlabs.com/browse/PUP-2782

[bschonec]

This still seems to be a problem. The hiera data here and here imply that you can specify multiple yum URLs in a single file but the module creates separate files in /etc/yum.repos.d. In addition, the target parameter isn't documented in the README.md.

Merge request here solves the problem.