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

Could not find class ::epel when declaring Letsencrypt class #290

Closed
Surowa opened this issue May 16, 2022 · 1 comment
Closed

Could not find class ::epel when declaring Letsencrypt class #290

Surowa opened this issue May 16, 2022 · 1 comment

Comments

@Surowa
Copy link

Surowa commented May 16, 2022

Affected Puppet, Ruby, OS and module versions/distributions

  • Puppet: 5.5.22
  • Ruby:
  • Distribution: CentOS 7 Core
  • Module version:

How to reproduce (e.g Puppet code you use)

class { 'letsencrypt':
config => {
email => 'email_address@domain.com',
server => "https://${server}/acme/directory",
}
}

What are you seeing

Error: Could not retrieve catalog from remote server: Error 500 on SERVER: Server Error: Evaluation Error: Error while evaluating a Resource Statement, Evaluation Error: Error while evaluating a Function Call, Could not find class ::epel for $node (file: /srv/puppet/environments/$envname/modules/letsencrypt/manifests/install.pp, line: 18, column: 5) (file: /srv/puppet/environments/$envname/modules/$modulename/manifests/init.pp, line: 46) on node $node

What behaviour did you expect instead

Being able to import an ::epel subclass or just being able to run the encrypt.

Output log

Any additional information you'd like to impart

@ekohl
Copy link
Member

ekohl commented May 21, 2022

This is a documented soft dependency: https://github.com/voxpupuli/puppet-letsencrypt#dependencies describes that you are responsible for having the EPEL module present in your environment. Perhaps it can be more explicit in saying that it is a soft dependency and a PR for that is welcome, but this is the desired workflow.

@ekohl ekohl closed this as not planned Won't fix, can't repro, duplicate, stale May 21, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants