From 85d1f33bb026e5543a4dfb535a87226b35690b36 Mon Sep 17 00:00:00 2001 From: Esoterydactyl Date: Fri, 5 Aug 2022 08:40:16 -0400 Subject: [PATCH] Add Chef resources * Update 101-chef.md * Update content/roadmaps/102-devops/content/105-infrastructure-as-code/102-configuration-management/101-chef.md Co-authored-by: Kamran Ahmed --- .../102-configuration-management/101-chef.md | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-) diff --git a/content/roadmaps/102-devops/content/105-infrastructure-as-code/102-configuration-management/101-chef.md b/content/roadmaps/102-devops/content/105-infrastructure-as-code/102-configuration-management/101-chef.md index 9f5836b05..3b3365f9f 100644 --- a/content/roadmaps/102-devops/content/105-infrastructure-as-code/102-configuration-management/101-chef.md +++ b/content/roadmaps/102-devops/content/105-infrastructure-as-code/102-configuration-management/101-chef.md @@ -1 +1,10 @@ -# Chef \ No newline at end of file +# Chef + +Emerging in 2009, [Chef](https://en.wikipedia.org/wiki/Progress_Chef) (now known as Progress Chef) is one of the earliest configuration management tools to gain popularity. Chef "Recipes" are written in Ruby, in a primarily [declarative](https://en.wikipedia.org/wiki/Declarative_programming) style. + +Chef requires that a client is installed on a server being managed. This client polls a Chef-Server regularly, to determine what its configuration should be. Chef-Solo is also available, a version of Chef that allows provisioning of a single node by running chef locally. + +A key tenet of Chef recipe design is the concept of [idempotence](https://en.wikipedia.org/wiki/Idempotence). All Chef recipes should be runnable multiple times and produce the same result - this is especially necessary in cases where the client/server model listed above is in use. This pattern of configuration management is highly influential for future declarative tools like Terraform and Cloud Formation. + +Chef Website +Chef Tutorial