-
-
Notifications
You must be signed in to change notification settings - Fork 46
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
comment property does not work #131
Comments
Can you show your Puppet code please? |
Like this: sysctl { 'net.ipv6.conf.default.accept_redirects':
ensure => 'present',
value => '0',
comment => "Disable ipv6 redirects",
} |
Are you using another sysctl module at the same time? |
It seem #129 indicates you are using another module, which provides a different, incompatible type. You need to choose which one you want to use (or ask @fiddyspence if he would depend on augeasproviders_sysctl for his resource type instead. |
Suggestion: Collaborate with @fiddyspence and fix the problem “Sometimes I think the surest sign that intelligent life exists elsewhere in the universe is that none of it has tried to contact us.” (Bill Waterson: Calvin & Hobbes) On Nov 17, 2014, at 09:19 AM, Raphaël Pinson [email protected] wrote:
|
I kind of agree that it's just a conflict here. The types/modules are named the same thing, and I'm not hugely inclined to rename the type. I'm also not a huge augeas fan, so migrating to using augeasproviders isn't really on my radar - I don't want the type to have that kind of external library dependency hence the ruby file munging. |
I was going to say we could share a common type, but then I had a closer look at @fiddyspence's module, and it really does just the same thing as this one, except without using Augeas. So, @linuxdan, what could be the reason for wanting to use both at the same time? |
Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Invalid parameter comment on Sysctl[net.ipv6.conf.default.accept_redirects] at /etc/puppet/modules/System_config/manifests/init.pp:252 on node devserver.example.com
The text was updated successfully, but these errors were encountered: