I'm late chiming in...

The moderate profile looks reasonable and is good as a default if we also
include the custom anonymization in some form. Per Chris's point, it would
likely be used by PSEs. It looks like that is the plan so I'm happy with
the work.




On Mon, Jul 22, 2013 at 8:59 AM, Ken Barber <notifications@github.com>wrote:

> In documentation/anonymization.markdown:
>
> > +
> > +This is useful if you really paranoid about what data you expose, but provides the least amount of usefulness for the consumer of such data depending on the activity they are trying to test.
> > +
> > +### Profile: moderate
> > +
> > +> **Note:** If no profile is specified, this is the default.
> > +
> > +The `moderate` profile attempts to be a bit smarter about what it anonymizes and is the recommended one for most cases. It operates different depending on the data type:
> > +
> > +* node name: is anonymized by default always
> > +* resource type name: the core types that are built-in to Puppet are not anonymized, including some common types from the modules: stdlib, postgresql, rabbitmq, puppetdb, apache, mrep, f5, apt, registry, concat and mysql. Any Puppet Enterprise core types names are also preserved. The goal here is to anonymize any custom or unknown resource type names as they may contain confidential information.
> > +* resource titles: all titles are anonymized expect for those belonging to Filebucket, Package, Service and Stage.
> > +* parameter names: are never anonymized
> > +* parameter values: everything is anonymized except for the values for `provider`, `ensure`, `noop`, `loglevel`, `audit` and `schedule`.
> > +* report log messages: are always anonymized
> > +* file names: are always anonymized
>
> Yeah, I'm doing it in a coarse grained way for obvious leaf nodes ... but
> not for parameter values.
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/puppetlabs/puppetdb/pull/558/files#r5322423>
> .
>



-- 
Thanks,

-j