-
-
Notifications
You must be signed in to change notification settings - Fork 99
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
Move lookup_options to hiera #134
Move lookup_options to hiera #134
Conversation
This allows the merge strategy to be overriden by users in their own hiera.
@rschemm Could you test this for me and report back? |
@@ -24,16 +24,12 @@ | |||
debug = <%= @debug %> | |||
quiet = <%= @quiet %> | |||
|
|||
<% if @_outputs -%> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A hash is always truthy
. I did consider changing it to unless @outputs.empty?
, but I don't think there's any point. The defaults aren't empty, and does having no inputs or outputs make a lot of sense?
common.eyaml
in roles/role1/common.eyaml
in envs/dev.eyaml
Testing with all inputs removed from hiera
Looks good to me |
This allows the merge strategy to be overriden by users in their own
hiera.