Configure merge behavior in data

We've updated our documentation to remove harmful terminology.
Sections

uses a key’s configured merge behavior in any lookup that doesn’t explicitly override it.

In any data source, including module data:

Use the lookup_options key to configure merge behavior.
Results
For example: 
# <ENVIRONMENT>/data/common.yaml
lookup_options:
  ntp::servers:     # Name of key
    merge: unique   # Merge behavior as a string
  "^profile::(.*)::users$": # Regexp: `$users` parameter of any profile class
    merge:          # Merge behavior as a hash
      strategy: deep
      merge_hash_arrays: true

uses the configured merge behaviors for these keys.

Note: The hiera_* functions always override configured merge behavior.
How helpful was this page?

If you leave us your email, we may contact you regarding your feedback. For more information on how Puppet uses your personal information, see our privacy policy.

Puppet sites use proprietary and third-party cookies. By using our sites, you agree to our cookie policy.