Jira (PUP-2163) yumrepo resource completely broken with 3.5 release

[Aaron Whiteside (JIRA)]

Title: Message Title

Aaron Whiteside commented on an issue   Re: yumrepo resource completely broken with 3.5 release Guys first off I want to thank you for the quick turn around on this issue, it's really good to know everyone is on top of this stuff! Ashley Penney For #2 the following resource definition will produce the error I mentioned.. yumrepo{ 'base': ensure => present, name => 'my base repo', baseurl => 'http://someurl', } here the title is the repo id I.e. [base] in the repo file, but when the name attribute is specified now the name becomes the repo id, so [my base repo] in the .repo file, and yum complains that there is no actual name=my base repo in .repo file. so the title should be used for the repo id, and the name attribute in the resource should not override this, it should only be used for the name= value in the .repo file. You may want to introduce another resource attribute to override the title, maybe repo_id => 'something'? Add Comment   Puppet / PUP-2163 yumrepo resource completely broken with 3.5 release 1. Any attribute that can take 'absent' as a value, either complains about it being invalid or puts the actual text value 'absent' in to the produced repo file. http://docs.puppetlabs.com/references/latest/type.html#yumrepo for example: exclude => absent ends up looking like exclude=absent in the .repo file. 2. yumrepo resource title sho... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.