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

Unknown resource type: 'ini_setting' #347

Open
jerome2710 opened this issue May 13, 2024 · 2 comments
Open

Unknown resource type: 'ini_setting' #347

jerome2710 opened this issue May 13, 2024 · 2 comments
Labels

Comments

@jerome2710
Copy link

As a Puppet-beginner I am trying to setup a simple code for managing nginx locations with SSL-certificates on a server. My setup consists of a Puppet server, with a remote repository pushing changes with r10k and for now 1 client fetching its configuration.

After adding mod 'puppet-letsencrypt', '11.0.0' to my Puppetfile, setting up letsencrypt::email and one certificate, puppet agent -t --noop fails with the following message:

Error: Could not retrieve catalog from remote server: Error 500 on SERVER: Server Error: Evaluation Error: Error while evaluating a Resource Statement, Unknown resource type: 'ini_setting' (file: /etc/puppetlabs/code/environments/production/modules/letsencrypt/manifests/config.pp, line: 32, column: 3) on node X

I forgot to check the dependencies from the metadata.json and now added mod 'puppetlabs-inifile', '6.1.1' to my Puppetfile as well. However, after pushing and re-running puppet agent -t --noop, I still get the same result.

In the stated directory of die Puppet server, I can actually see both the letsencrypt and inifile modules;

Scherm­afbeelding 2024-05-13 om 15 43 25

I am probably making a rookie mistake, could someone point me in the right direction?

@kenyon
Copy link
Member

kenyon commented May 13, 2024

Try adding --generate-types to your r10k deploy environment command line.

@jerome2710
Copy link
Author

Try adding --generate-types to your r10k deploy environment command line.

Will do and let you know if the problem reoccurs! Thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants