-
Notifications
You must be signed in to change notification settings - Fork 238
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
Subsystem setting broken with use_augeas => true #376
Comments
Thanks for the detailed report. To get this working, puppet-ssh/manifests/server/config.pp Line 21 in f8a3110
It might be enough to check if the key matches I'll try to come up with a PR |
@saz Sorry but we've teared down that puppet environment about a month ago so I can't test it :( |
Thanks for the feedback. My change seems to be working, so I'll just merge it. |
Using module version 11.2.0.
First problem we notices was that when using
use_augeas => true
, $default_options is ignored.A work around was to replace
$options
on line L78 in manifests/server.pp withdeep_merge($default_options, $options)
. This enables defaults_options and the possibility to override them via the manifest or hieradata.However, we got an error from
Puppet::Type::Sshd_config::ProviderAugeas
statingSsh::Server::Config/Sshd_config[Subsystem]: Could not evaluate: Failed to save Augeas tree to file. See debug logs for details
Looking at the debug output I noticed
/Subsystem/
missing from the pattern. Investigated further and found that in the'puppet-augeasproviders_ssh', '6.0.0'
this seems to be in another provider,sshd_config_subsystem
as commented here, (not sure how to use the correct terminology, but hope it makes sense).I'm not capable enough to conjure a solution, but maybe this info can help someone that hits the same issue. I'll just use the default
use_augeas => false
as a viable solution.The text was updated successfully, but these errors were encountered: