Jira (PUP-2031) unless_uid on user is completely broken wrt ranges

[Henrik Lindberg (JIRA)]

Title: Message Title

Henrik Lindberg commented on an issue   Re: unless_uid on user is completely broken wrt ranges Felix Frank yes, the functionality is in place, but users must add the 'rgen' gem since the implementation i in the "future part". Does not require using the future parser for everything else though. If this is in a module, it should be fine to require users to also have rgen installed since it is opt in and does not disturb anything else. Usage inside the function is also very simple: the_type = Puppet::Pops::Types::TypeParser.new.parse(type_in_string_form) The result is an Puppet::Pops::Types::PIntegerType which has methods to: get the range as a [from, to] array support iteration (unless one of the values is Infinity) get the size (smallest possible size is 1, an empty range can not be expressed Infinity is a special value in Ruby and it can be used in arithmetic. Add Comment   Puppet / PUP-2031 unless_uid on user is completely broken wrt ranges A PR was merged in PUP-1447 that adds an unless_uid option. However, the implementation is completely broken: This works: {noformat}   resources { 'user':     purge => true,     unless_system_user => true,     unless_uid => 20000,   } {noformat} Broken: {noformat}   resources { 'user':     purge => true, ... 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.