{"id":4942,"date":"2018-05-03T06:31:23","date_gmt":"2018-05-03T06:31:23","guid":{"rendered":"http:\/\/www.scmgalaxy.com\/tutorials\/?p=4942"},"modified":"2021-11-17T10:35:25","modified_gmt":"2021-11-17T10:35:25","slug":"run_list-and-env_run_list-explanined-in-chef-role","status":"publish","type":"post","link":"https:\/\/www.devopsschool.com\/blog\/run_list-and-env_run_list-explanined-in-chef-role\/","title":{"rendered":"run_list and env_run_list explanined in chef role"},"content":{"rendered":"

\"\"<\/p>\n

run-list<\/strong>
\nA run-list defines all of the information necessary for Chef to configure a node into the desired state. A run-list may include roles and\/or recipes.<\/p>\n

A run-list must be in one of the following formats: fully qualified, cookbook, or default. Both roles and recipes must be in quotes, for example:<\/p>\n

[code]’role[NAME]’
\n‘recipe[COOKBOOK::RECIPE]’
\n‘recipe[COOKBOOK::RECIPE],COOKBOOK::RECIPE,role[NAME]'[\/code]<\/p>\n

env_run_list<\/strong>
\nWhen you specify the env_run_list in role and the chef-client will pick up the _default run-list if env_run_list[environment_name] is null or nonexistent. env_run_list is only for roles.The env run list is an override, so it totally replaces the default non-env run list if the env matches.<\/p>\n

[code]{
\n “name”: “webserver”,
\n “default_attributes”: {
\n },
\n “json_class”: “Chef::Role”,
\n “env_run_lists”: {
\n “production”: [],
\n “preprod”: [],
\n “test”: [ “role[base]”, “recipe[apache]” “recipe[apache::copy_test_configs]” ],
\n “dev”: [ “role[base]”, “recipe[apache]”, “recipe[apache::copy_dev_configs]” ]
\n },
\n “run_list”: [ “role[base]”, “recipe[apache]” ],
\n “description”: “The webserver role”,
\n “chef_type”: “role”,
\n “override_attributes”: {
\n }
\n}[\/code]<\/p>\n

where:<\/strong><\/p>\n