-
-
Notifications
You must be signed in to change notification settings - Fork 881
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
Defining vhosts in Hiera #566
Comments
So either I am missing the point, or you have to do this: class { "nginx":
geo_mappings => hiera("nginx::geo_mappings", {}),
string_mappings => hiera("nginx::string_mappings", {}),
nginx_locations => hiera("nginx::nginx_locations", {}),
nginx_mailhosts => hiera("nginx::nginx_mailhosts", {}),
nginx_upstreams => hiera("nginx::nginx_upstreams", {}),
nginx_vhosts => hiera("nginx::nginx_vhosts", {}),
nginx_vhosts_defaults => hiera("nginx::nginx_vhosts_defaults", {}),
}
include nginx::config Either I am doing things wrong, and if so, please correct me… or seriously, document this, in the README, or hiera doc file, in big ass letters. I assume these aren't the defaults as it would cause hiera-less users errors? |
I seem to have had something similar, and i fixed it by changing |
@stevelacey: is this still a problem, or can we close this out? |
I don't use Puppet anymore, so it's not a problem for me at least 😉 |
I am probably just doing Hiera wrong... but this does nothing for me:
hiera/common.yaml:
In my node:
I think the Hiera is at least right my worker_processes gets set, and the following is returned if I run this on the master:
Do I need to define something specific to the vhost or vhosts in general in my manifest to trigger it pulling in the vhost settings?
nginx::resource::vhost { $::fqdn: }
moans about no params passed – i.e. it can't see thewww_root
.The text was updated successfully, but these errors were encountered: