You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This cookbook provides new chef resource types which can be used by other recipes. However, the cookbook does not have any recipes so it doesn't actually do anything on it's own. This is perfectly fine in most situations.
However, there are use cases where it doesn't make sense to create a new cookbook just for the purpose of creating a single entry in /etc/hosts. Or there isn't an existing cookbook which would be appropriate for adding a recipe that configures hostsfile_entry resources.
Those simple use cases would benefit if cookbook hostsfile allowed attribute-driven configuration. No new cookbooks would be required. Simply including hostsfile::default in the runlist and setting some attributes in environment/role/recipe would be enough.
The text was updated successfully, but these errors were encountered:
This cookbook provides new chef resource types which can be used by other recipes. However, the cookbook does not have any recipes so it doesn't actually do anything on it's own. This is perfectly fine in most situations.
However, there are use cases where it doesn't make sense to create a new cookbook just for the purpose of creating a single entry in /etc/hosts. Or there isn't an existing cookbook which would be appropriate for adding a recipe that configures hostsfile_entry resources.
Those simple use cases would benefit if cookbook hostsfile allowed attribute-driven configuration. No new cookbooks would be required. Simply including hostsfile::default in the runlist and setting some attributes in environment/role/recipe would be enough.
The text was updated successfully, but these errors were encountered: