<commit_before># Puppet-Hiera deep merge on demand

[![Build Status](https://travis-ci.org/gandi/puppet-hiera-deep-merge.svg?branch=master)](https://travis-ci.org/gandi/puppet-hiera-deep-merge)

## Why ?

Hiera 1.2 has bring the [deep_merge behavior](https://docs.puppetlabs.com/hiera/1/lookup_types.html#deep-merging-in-hiera--120) which is an large enhancement for managing stuff in Hiera. But merge behavior is a global settings in hiera and when migrating a large puppet code base, this may be error-prone. For this purpose, this module provides a new function named ``hiera_hash_merge`` which will use the `deep_merge` behavior but does not need a global switch.

## Usage

common.yaml:<commit_msg>Fixup travis badges<commit_after># Puppet-Hiera deep merge on demand

[![Build Status](https://travis-ci.org/Gandi/puppet-hiera-deep-merge.svg?branch=master)](https://travis-ci.org/Gandi/puppet-hiera-deep-merge)

## Why ?

Hiera 1.2 has bring the [deep_merge behavior](https://docs.puppetlabs.com/hiera/1/lookup_types.html#deep-merging-in-hiera--120) which is an large enhancement for managing stuff in Hiera. But merge behavior is a global settings in hiera and when migrating a large puppet code base, this may be error-prone. For this purpose, this module provides a new function named ``hiera_hash_merge`` which will use the `deep_merge` behavior but does not need a global switch.

## Usage

common.yaml:
{'fraction_non_alphanumeric': 0.10764872521246459, 'fraction_numerical': 0.0084985835694051, 'mean_word_length': 4.863070539419087, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 6, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '585546', 'n_tokens_mistral': 464, 'n_tokens_neox': 449, 'n_words': 147}