Puppet 2.7 that we support runs on ruby 1.8.5 or 1.8.7 As a consequence, the hash when serialized by the .to_yaml function can go in any order in the rendered string. To avoid that we monkey patch the to_yaml function to sort the hash by key every time if the ruby we are using is < 1.9. It should avoid puppet to regenerate the same resource over and over just because of some stupid ordering issues.
* Multiple typos * We use integrations as subclasses not defines * In puppet you cannot reassign a variable (mongo integration) * Directory integration needed a proper name to tag metrics * Fixed hash access in ruby (not with the dot method) * Use new template variables with @ prefix
Manually cherry-picked pull #32 work and only kept the changes that concerned log_level. The other changes that concerned upgrading puppet DSL or style have been merged to the branch soon to be released as v1.0.0 and merged to master as such, leaving this obsolete code for very old puppet installs
Conflicts: manifests/init.pp manifests/integrations/elasticsearch.pp templates/datadog.conf.erb * Adds jenkins integration * Adds mongo integration * Adds nginx integration * Adds process integration * Adds parameters for the agent deployment * Move conf.d agent files into a single directory
Enable the user to set up the master as a proxy for instance.