Skip to content
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

Duplicate declaration when using class ssh::server directly #335

Closed
algolsigfrid opened this issue Jul 28, 2022 · 2 comments
Closed

Duplicate declaration when using class ssh::server directly #335

algolsigfrid opened this issue Jul 28, 2022 · 2 comments

Comments

@algolsigfrid
Copy link

Apologies because this might be more an user error than a bug.

I am trying to use the class ssh::server directly from within a profile class and I am getting a duplicate declaration error. The documentation for the module suggests that I should be able to use the ssh::server class directly and I do not understand what I am doing wrong.

class profile::ssh::server {
  
  class { 'ssh::server':
    storeconfigs_enabled => true,
    validate_sshd_file   => true,
    options              => {
      'AddressFamily'                   => 'inet',
       ... ... ... more options here ....
     },
  }
}

And the error message indicates a duplicate declaration at /site/profile/manifests/ssh/server.pp (my profile class) and /modules/ssh/manifests/init.pp (this module managed by r10k)

I am following the example documentation here
https://github.com/saz/puppet-ssh/tree/v9.0.0#server-only

I have searched all over my control repository and I do not see any other references to either class ssh or class ssh::server

Any pointers are appreciated.

Thank you in advance for your help.

@alexskr
Copy link

alexskr commented Sep 2, 2022

This functionality broke in v9.0.0 release. The fix is in place but has not been released yet.

@saz
Copy link
Owner

saz commented Oct 31, 2022

I've just release v10.0.0 which should resolve this issue

@saz saz closed this as completed Oct 31, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants