-
-
Notifications
You must be signed in to change notification settings - Fork 878
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
Adding a simple vhost not as simple as it seems #887
Comments
Are you using the future parser? If so, this looks like a duplicate of #806 |
no it's we're not using the future parser. |
running puppet master in version 4.6.0 so definetly future parser |
@sfozz: Is this issue still affecting you, or did you ever find a solution? |
Nope not found the solution yet... Just to confirm I'm not using the future parser
|
I think we're trying to fix it so that invoking 'nginx' class directly will work (and possibly so parameters pass through), as well as replacing some of the language urging use of hiera. That said, assuming you're not using hiera to define stuff in nginx::config, have you tried following the pattern outlined under "I (cannot/do not want to) use Hiera" at: |
at least v0.6.0 has no with If you can provide reproduction steps in a clean environment please reopen. |
Affected Puppet, Ruby, OS and module versions/distributions
How to reproduce (e.g Puppet code you use)
What are you seeing
What behaviour did you expect instead
Output log
Any additional information you'd like to impart
I've also put a:
require => Class[::nginx::config],
in the vhost resource, but that also fails.
The text was updated successfully, but these errors were encountered: