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

Allow weak SSL verification for apt_key #849

Merged
merged 1 commit into from
Mar 20, 2019
Merged

Allow weak SSL verification for apt_key #849

merged 1 commit into from
Mar 20, 2019

Conversation

tuxmea
Copy link

@tuxmea tuxmea commented Mar 20, 2019

@eimlav eimlav added the feature label Mar 20, 2019
@eimlav
Copy link

eimlav commented Mar 20, 2019

Adhoc ran successfully so I'm going to go ahead and merge. Thanks for contributing @tuxmea :)

Screen Shot 2019-03-20 at 13 39 51

@eimlav eimlav merged commit d2ae49f into puppetlabs:master Mar 20, 2019
@tuxmea tuxmea deleted the apt_key_weak_ssl branch March 20, 2019 14:19
@kenyon
Copy link

kenyon commented Jun 2, 2019

This change causes "Error: no parameter named 'weak_ssl'": https://tickets.puppetlabs.com/browse/MODULES-9209

@tuxmea
Copy link
Author

tuxmea commented Jun 4, 2019

This change causes "Error: no parameter named 'weak_ssl'": https://tickets.puppetlabs.com/browse/MODULES-9209

This could be related to environment leaking when having two environments with different versions of a type/provider:
https://puppet.com/docs/puppet/5.3/environments_about.html#troubleshooting-environment-leaks

Are you running puppet generate types after r10k deployment?

@kenyon
Copy link

kenyon commented Jun 4, 2019

It seems that simply restarting puppetserver after upgrading modules fixed it. I guess that is standard procedure.

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

Successfully merging this pull request may close these issues.

3 participants