Move configuration of lookup merge behavior into Hiera lookup_options. #99
Conversation
|
Any progress on this? It would be nice to have it solved |
|
Dear @Cova, thanks for the PR! This is pccibot, your friendly Vox Pupuli GitHub Bot. I noticed that your pull request contains merge conflict. Can you please rebase? You can find my sourcecode at voxpupuli/vox-pupuli-tasks |
1 similar comment
|
Dear @Cova, thanks for the PR! This is pccibot, your friendly Vox Pupuli GitHub Bot. I noticed that your pull request contains merge conflict. Can you please rebase? You can find my sourcecode at voxpupuli/vox-pupuli-tasks |
|
Dear @Cova, thanks for the PR! This is pccibot, your friendly Vox Pupuli GitHub Bot. I noticed that your pull request contains merge conflict. Can you please rebase? You can find my sourcecode at voxpupuli/vox-pupuli-tasks |
|
Dear @Cova, thanks for the PR! This is pccibot, your friendly Vox Pupuli GitHub Bot. I noticed that your pull request contains merge conflict. Can you please rebase? You can find my sourcecode at voxpupuli/vox-pupuli-tasks |
1 similar comment
|
Dear @Cova, thanks for the PR! This is pccibot, your friendly Vox Pupuli GitHub Bot. I noticed that your pull request contains merge conflict. Can you please rebase? You can find my sourcecode at voxpupuli/vox-pupuli-tasks |
|
Sorry I didn't notice this PR when I wrote #134 |
This fixes my issue #98 in a way that provides a (I think) sane default, and allows easy per-user overrides. With the basics setup, this could also be the base of moving all of the default values from params.pp into a few yaml files.
My inputs are very simple and have no problems also being merged this way - but its possible for more complicated setups that the inputs should stay with normal deep merge without the 'merge_hash_arrays' enabled by default.