You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For anyone using Ruby in their environments, using the r10k module presents a problem because of the way that ruby is included. It basically means that anyone doing an 'include ruby' anywhere in their puppet code is going to get a duplicate resource error.
Moving the to 'include ruby' here means that people can use ruby elsewhere also, though it doesn't solve the parameter being passed.
The text was updated successfully, but these errors were encountered:
Well for the time being we could wrap it to check the version of puppet as the parent bug of my original reference bug that required is not relevant for for anything thats not 3.2.3+
if versioncmp($::puppetversion,'3.2.2') > 0 {
class { '::ruby':
rubygems_update => false,
}
} else {
include ruby
}
For anyone using Ruby in their environments, using the r10k module presents a problem because of the way that ruby is included. It basically means that anyone doing an 'include ruby' anywhere in their puppet code is going to get a duplicate resource error.
Moving the to 'include ruby' here means that people can use ruby elsewhere also, though it doesn't solve the parameter being passed.
The text was updated successfully, but these errors were encountered: