devops:chef
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| devops:chef [2016/04/12 07:20] – skipidar | devops:chef [2023/11/01 07:15] (current) – ↷ Page moved from camunda:devops:chef to devops:chef skipidar | ||
|---|---|---|---|
| Line 27: | Line 27: | ||
| |CookBook| A collection of receipts. E.g. " | |CookBook| A collection of receipts. E.g. " | ||
| |Roles|Role can be assigned to a node. \\ A role is a way to define certain patterns and processes that exist across nodes in an organization as belonging to a single job function. \\ When a chef-client runs, it merges its own attributes and run-lists with those contained within each assigned role.| | |Roles|Role can be assigned to a node. \\ A role is a way to define certain patterns and processes that exist across nodes in an organization as belonging to a single job function. \\ When a chef-client runs, it merges its own attributes and run-lists with those contained within each assigned role.| | ||
| + | |Databag|< | ||
| + | |||
| + | A data bag is a container of related data bag items, where each individual data bag item is a JSON file. knife can load a data bag item by specifying the name of the data bag to which the item belongs and then the filename of the data bag item. | ||
| + | |||
| + | When the chef-repo is cloned from GitHub, the following occurs: | ||
| + | * A directory named data_bags is created. | ||
| + | * For each data bag, a sub-directory is created that has the same name as the data bag. | ||
| + | * For each data bag item, a JSON file is created and placed in the appropriate sub-directory. | ||
| + | </ | ||
devops/chef.1460445607.txt.gz · Last modified: (external edit)