diff options
| author | Claire McQuin <claire@getchef.com> | 2014-05-13 14:46:49 -0700 |
|---|---|---|
| committer | Claire McQuin <claire@getchef.com> | 2014-05-15 14:04:19 -0700 |
| commit | 4c48ed4a014480cbb34091df3c79600bd3b7378d (patch) | |
| tree | 80df26071729e2f048061a8e99b6f92674406c08 | |
| parent | 2f51b28f0a0178826524efdc20b6f41048470890 (diff) | |
| download | chef-4c48ed4a014480cbb34091df3c79600bd3b7378d.tar.gz | |
Update for whitelist use.
| -rw-r--r-- | DOC_CHANGES.md | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/DOC_CHANGES.md b/DOC_CHANGES.md index c9b4d3e86a..2959cd63ea 100644 --- a/DOC_CHANGES.md +++ b/DOC_CHANGES.md @@ -71,3 +71,5 @@ If your config file looks like `automatic_attribute_whitelist = {}`, then none o The default behavior is for the node to save all the attribute data. This can be ensured by setting your whitelist filter to `nil`. Note that only the keys in this has will be used. If the values are anything other than a hash, they are ignored. You cannot magically morph these config options into a blacklist by putting `false` as a value in the whitelist. + +We recommend only using `automatic_attribute_whitelist` to reduce the size of the system data being stored for nodes, and discourage the use of the other attribute whitelists except by advanced users. |