raucao
301565b910
Move allowed node attrs to config file, apply automatically
...
This moves the whitelist for nodes' "normal" attributes to a config
file, which is loaded live during every run and applied in memory in
case the node's local file hasn't been updated before the client run.
Fixes allowed attributes being overwritten/removed in the node info
JSON files.
2026-07-05 17:07:56 +02:00
cc91aab155
Use the new way of setting attribute whitelists
2023-07-17 18:06:23 +02:00
d79dcd8e65
Deploy kosmos assets with Openresty
2023-07-12 20:36:12 +02:00
51163ca3a3
Whitelist Chef attributes for newer client versions
2022-10-21 10:46:16 +02:00
basti
396fe6e714
Whitelist ejabberd custom node attributes
...
fixes #256
2020-12-11 19:07:06 +01:00
d029ee91be
Move the generate options to config.rb at the root of the repo
...
This has been the only way I managed to make `chef generate cookbook
COOKBOOK_NAME` set the default values
This is not documented, there is an issue open about it:
https://github.com/chef/chef-cli/issues/54
2019-12-27 11:33:05 +01:00
basti
8d78d41af7
Use MIT as default cookbook license
...
And improve the author name, making it more consistent with the rest of
the repo.
2019-12-18 20:19:42 +01:00
8fdafa1484
Set attribute whitelists for Knife-Zero
...
This prevents all attributes to be written in the node files. We don't
want that data stored in git.
See https://knife-zero.github.io/40_configuration/
2019-10-10 12:34:55 +02:00
f5858a8a6e
Remove unneeded setting
...
In Chef 15 local_mode is enough
2019-10-10 12:34:08 +02:00
20f6e9e04d
Delete config for knife-solo
2019-10-08 18:17:34 +02:00
3c05f172de
Add the cookbooks dir to the load path for Knife-Zero
2019-10-08 18:17:34 +02:00
99fc183172
Do not vendor cookbooks using Berkshelf anymore
...
Instead, use the Berkshelf support in knife-solo and the
vagrant-berkshelf plugin on Vagrant
2019-04-11 18:16:28 +02:00
raucao
Greg Karékinian
Râu Cao
basti
