Experimental Features: The Data Binder
Included in Puppet Enterprise 3.2. A newer version is available; see the version menu above for details.
Warning: This document describes an experimental feature, which is not officially supported and is not considered ready for production. See here for more information about experimental features in Puppet, especially if you are using Puppet Enterprise.
Status: The redesigned data binder is available in Puppet 3.3.0 and later.
Based on the feedback from users so far, we’ve decided that the current design for the data binder is a dead end. We do not plan to enable the functionality you can test today in a future Puppet release. However, we are still researching and investigating more more powerful ways to look up and interact with data in Puppet, and the lessons we learned from the current implementation will inform future efforts.
Currently, we recommend against enabling the data binder in a production deployment. As of Puppet 3.4, it still carries a massive performance penalty in catalog compilation (as it requires the future parser); additionally, it adds significant complexity to your configuration using a very non-final user interface.
Enabling the Data Binder
To enable the data binder:
- Make sure you are using Puppet 3.3.0 or later.
- On your puppet master(s), follow the instructions for enabling the future parser.
- On your puppet master(s), set
binder = truein the
[main]block of puppet.conf.
Using the Data Binder
To experiment with the data binder, you will need to follow the examples available in the “ARM-9” feature proposal.
The feature proposal is the only documentation available for the redesigned data binder. Since we’ve deemed the current interface a dead end, we do not plan to invest in more user-centric documentation.