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

ssl::server_name syntax error #117

Closed
DidgeriDude opened this issue Jan 24, 2019 · 2 comments
Closed

ssl::server_name syntax error #117

DidgeriDude opened this issue Jan 24, 2019 · 2 comments

Comments

@DidgeriDude
Copy link

DidgeriDude commented Jan 24, 2019

Not sure if this is an issue with puppet or the module, but I am unable to use 'ssl::server_name' due to a syntax error.

Affected Puppet, Ruby, OS and module versions/distributions

  • Puppet: 5.5.2
  • Ruby: 2.5.1
  • Distribution: Ubuntu 18.04
  • Module version: 1.0.0

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

squid::acl {'whitelisted_https_sites': type => 'ssl::server_name', entries => $whitelisted_sites, }

Also fails when escaping the characters

squid::acl {'whitelisted_https_sites': type => 'ssl\:\:server_name', entries => $whitelisted_sites, }

What are you seeing

Error: Evaluation Error: Error while evaluating a Resource Statement, Evaluation Error: Error while evaluating a Function Call, Concat::Fragment['squid_acl_allowed_https_websites']: 'order' cannot contain '/', ':', or '\n'. (file: /root/test/modules/concat/manifests/fragment.pp, line: 27, column: 5) (file: /root/test/modules/squid/manifests/acl.pp, line: 15) on node squid

Is there any way to bypass this? I also tried using squid::extra_config_section.

@ekohl
Copy link
Member

ekohl commented Jan 24, 2019

8f8b7e3#diff-c9e6a3913500ff4c764544544068d6c4 should solve this. It's also supposed to be part of 1.0.0 so it confuses me why this is a problem. Could you confirm that patch is part of the code?

@DidgeriDude
Copy link
Author

You are right. I thought the version was 1.0.0. However, I might have not checked. I'm sorry for this. This issue can be closed.

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

2 participants