microwave 11.400.5 → 11.400.6

Sign up to get free protection for your applications and to get access to all the features.
Files changed (118) hide show
  1. data/VERSION +1 -1
  2. data/lib/chef/daemon.rb +0 -2
  3. metadata +3 -118
  4. data/distro/README +0 -2
  5. data/distro/arch/etc/conf.d/chef-client.conf +0 -5
  6. data/distro/arch/etc/conf.d/chef-expander.conf +0 -8
  7. data/distro/arch/etc/conf.d/chef-server-webui.conf +0 -10
  8. data/distro/arch/etc/conf.d/chef-server.conf +0 -10
  9. data/distro/arch/etc/conf.d/chef-solr.conf +0 -8
  10. data/distro/arch/etc/rc.d/chef-client +0 -90
  11. data/distro/arch/etc/rc.d/chef-expander +0 -78
  12. data/distro/arch/etc/rc.d/chef-server +0 -78
  13. data/distro/arch/etc/rc.d/chef-server-webui +0 -78
  14. data/distro/arch/etc/rc.d/chef-solr +0 -78
  15. data/distro/common/html/chef-client.8.html +0 -145
  16. data/distro/common/html/chef-expander.8.html +0 -164
  17. data/distro/common/html/chef-expanderctl.8.html +0 -146
  18. data/distro/common/html/chef-server-webui.8.html +0 -185
  19. data/distro/common/html/chef-server.8.html +0 -182
  20. data/distro/common/html/chef-shell.1.html +0 -286
  21. data/distro/common/html/chef-solo.8.html +0 -191
  22. data/distro/common/html/chef-solr.8.html +0 -165
  23. data/distro/common/html/knife-bootstrap.1.html +0 -241
  24. data/distro/common/html/knife-client.1.html +0 -219
  25. data/distro/common/html/knife-configure.1.html +0 -170
  26. data/distro/common/html/knife-cookbook-site.1.html +0 -241
  27. data/distro/common/html/knife-cookbook.1.html +0 -384
  28. data/distro/common/html/knife-data-bag.1.html +0 -238
  29. data/distro/common/html/knife-environment.1.html +0 -267
  30. data/distro/common/html/knife-exec.1.html +0 -134
  31. data/distro/common/html/knife-index.1.html +0 -125
  32. data/distro/common/html/knife-node.1.html +0 -250
  33. data/distro/common/html/knife-role.1.html +0 -200
  34. data/distro/common/html/knife-search.1.html +0 -288
  35. data/distro/common/html/knife-ssh.1.html +0 -156
  36. data/distro/common/html/knife-status.1.html +0 -128
  37. data/distro/common/html/knife-tag.1.html +0 -137
  38. data/distro/common/html/knife.1.html +0 -315
  39. data/distro/common/man/man1/chef-shell.1 +0 -220
  40. data/distro/common/man/man1/knife-bootstrap.1 +0 -201
  41. data/distro/common/man/man1/knife-client.1 +0 -99
  42. data/distro/common/man/man1/knife-configure.1 +0 -88
  43. data/distro/common/man/man1/knife-cookbook-site.1 +0 -145
  44. data/distro/common/man/man1/knife-cookbook.1 +0 -345
  45. data/distro/common/man/man1/knife-data-bag.1 +0 -136
  46. data/distro/common/man/man1/knife-environment.1 +0 -178
  47. data/distro/common/man/man1/knife-exec.1 +0 -43
  48. data/distro/common/man/man1/knife-index.1 +0 -29
  49. data/distro/common/man/man1/knife-node.1 +0 -134
  50. data/distro/common/man/man1/knife-role.1 +0 -88
  51. data/distro/common/man/man1/knife-search.1 +0 -280
  52. data/distro/common/man/man1/knife-ssh.1 +0 -79
  53. data/distro/common/man/man1/knife-status.1 +0 -29
  54. data/distro/common/man/man1/knife-tag.1 +0 -43
  55. data/distro/common/man/man1/knife.1 +0 -285
  56. data/distro/common/man/man8/chef-client.8 +0 -104
  57. data/distro/common/man/man8/chef-expander.8 +0 -97
  58. data/distro/common/man/man8/chef-expanderctl.8 +0 -62
  59. data/distro/common/man/man8/chef-server-webui.8 +0 -155
  60. data/distro/common/man/man8/chef-server.8 +0 -147
  61. data/distro/common/man/man8/chef-solo.8 +0 -158
  62. data/distro/common/man/man8/chef-solr.8 +0 -122
  63. data/distro/common/markdown/README +0 -3
  64. data/distro/common/markdown/man1/chef-shell.mkd +0 -195
  65. data/distro/common/markdown/man1/knife-bootstrap.mkd +0 -141
  66. data/distro/common/markdown/man1/knife-client.mkd +0 -103
  67. data/distro/common/markdown/man1/knife-configure.mkd +0 -70
  68. data/distro/common/markdown/man1/knife-cookbook-site.mkd +0 -123
  69. data/distro/common/markdown/man1/knife-cookbook.mkd +0 -263
  70. data/distro/common/markdown/man1/knife-data-bag.mkd +0 -121
  71. data/distro/common/markdown/man1/knife-environment.mkd +0 -151
  72. data/distro/common/markdown/man1/knife-exec.mkd +0 -42
  73. data/distro/common/markdown/man1/knife-index.mkd +0 -30
  74. data/distro/common/markdown/man1/knife-node.mkd +0 -130
  75. data/distro/common/markdown/man1/knife-role.mkd +0 -85
  76. data/distro/common/markdown/man1/knife-search.mkd +0 -180
  77. data/distro/common/markdown/man1/knife-ssh.mkd +0 -69
  78. data/distro/common/markdown/man1/knife-status.mkd +0 -36
  79. data/distro/common/markdown/man1/knife-tag.mkd +0 -39
  80. data/distro/common/markdown/man1/knife.mkd +0 -213
  81. data/distro/common/markdown/man8/chef-client.mkd +0 -74
  82. data/distro/common/markdown/man8/chef-expander.mkd +0 -82
  83. data/distro/common/markdown/man8/chef-expanderctl.mkd +0 -58
  84. data/distro/common/markdown/man8/chef-server-webui.mkd +0 -121
  85. data/distro/common/markdown/man8/chef-server.mkd +0 -121
  86. data/distro/common/markdown/man8/chef-solo.mkd +0 -107
  87. data/distro/common/markdown/man8/chef-solr.mkd +0 -89
  88. data/distro/debian/etc/default/chef-client +0 -4
  89. data/distro/debian/etc/default/chef-expander +0 -8
  90. data/distro/debian/etc/default/chef-server +0 -9
  91. data/distro/debian/etc/default/chef-server-webui +0 -9
  92. data/distro/debian/etc/default/chef-solr +0 -8
  93. data/distro/debian/etc/init.d/chef-client +0 -210
  94. data/distro/debian/etc/init.d/chef-expander +0 -176
  95. data/distro/debian/etc/init.d/chef-server +0 -122
  96. data/distro/debian/etc/init.d/chef-server-webui +0 -123
  97. data/distro/debian/etc/init.d/chef-solr +0 -176
  98. data/distro/debian/etc/init/chef-client.conf +0 -17
  99. data/distro/debian/etc/init/chef-expander.conf +0 -17
  100. data/distro/debian/etc/init/chef-server-webui.conf +0 -17
  101. data/distro/debian/etc/init/chef-server.conf +0 -17
  102. data/distro/debian/etc/init/chef-solr.conf +0 -17
  103. data/distro/redhat/etc/init.d/chef-client +0 -121
  104. data/distro/redhat/etc/init.d/chef-expander +0 -104
  105. data/distro/redhat/etc/init.d/chef-server +0 -112
  106. data/distro/redhat/etc/init.d/chef-server-webui +0 -112
  107. data/distro/redhat/etc/init.d/chef-solr +0 -104
  108. data/distro/redhat/etc/logrotate.d/chef-client +0 -8
  109. data/distro/redhat/etc/logrotate.d/chef-expander +0 -8
  110. data/distro/redhat/etc/logrotate.d/chef-server +0 -8
  111. data/distro/redhat/etc/logrotate.d/chef-server-webui +0 -8
  112. data/distro/redhat/etc/logrotate.d/chef-solr +0 -8
  113. data/distro/redhat/etc/sysconfig/chef-client +0 -15
  114. data/distro/redhat/etc/sysconfig/chef-expander +0 -7
  115. data/distro/redhat/etc/sysconfig/chef-server +0 -14
  116. data/distro/redhat/etc/sysconfig/chef-server-webui +0 -14
  117. data/distro/redhat/etc/sysconfig/chef-solr +0 -8
  118. data/distro/windows/service_manager.rb +0 -164
@@ -1,121 +0,0 @@
1
- knife-data-bag(1) -- Store arbitrary data on a Chef Server
2
- ========================================
3
-
4
- ## SYNOPSIS
5
-
6
- __knife__ __data bag__ _sub-command_ _(options)_
7
-
8
- ## DESCRIPTION
9
- Data bags are stores of arbitrary JSON data. Each data bag is a
10
- collection that may contain many items. Data Bag Items are indexed by
11
- the Chef Server and can be searched via __knife-search__(1).
12
-
13
- Data bags are available to all nodes configured by __chef-client__(8),
14
- and are therefore a convenient mechanism to store global information,
15
- such as lists of administrative accounts that should be configured on
16
- all hosts.
17
-
18
- ## DATA BAG SUB-COMMANDS
19
-
20
- ## CREATE
21
- __knife data bag create__ _bag name_ [item id] _(options)_
22
-
23
- * `-s`, `--secret SECRET`:
24
- A secret key used to encrypt the data bag item. See __encryption support__ below.
25
- * `--secret-file SECRET_FILE`:
26
- The path to a file containing the secret key to be used to encrypt
27
- the data bag item.
28
-
29
- If _item id_ is given, creates a new, empty data bag item and opens it for
30
- editing in your editor. The data bag will be created if it does not
31
- exist.
32
-
33
- If _item id_ is not given, the data bag will be created.
34
-
35
- ## DELETE
36
- __knife data bag delete__ _bag name_ [item id] _(options)_
37
-
38
- Delete a data bag, or an item from a data bag.
39
-
40
- ## EDIT
41
- __knife data bag edit__ _bag name_ _item id_ _(options)_
42
-
43
- * `-s`, `--secret SECRET`:
44
- A secret key used to encrypt the data bag item. See __encryption support__ below.
45
- * `--secret-file SECRET_FILE`:
46
- The path to a file containing the secret key to be used to encrypt
47
- the data bag item.
48
-
49
- Edit an item in a data bag.
50
-
51
- ## FROM FILE
52
- __knife data bag from file__ _bag name_ _file_ _(options)_
53
-
54
- __knife data bag from file__ _bag name_ _file1_ _file2_ _file3_ _(options)_
55
-
56
- __knife data bag from file__ _bag name_ _folder_ _(options)_
57
-
58
- * `-s`, `--secret SECRET`:
59
- A secret key used to encrypt the data bag item. See __encryption support__ below.
60
- * `--secret-file SECRET_FILE`:
61
- The path to a file containing the secret key to be used to encrypt
62
- the data bag item.
63
-
64
- Load a data bag item from a JSON file. If _file_ is a relative or
65
- absolute path to the file, that file will be used. Otherwise, the _file_
66
- parameter is treated as the base name of a data bag file in a Chef
67
- repository, and `knife` will search for the file in
68
- `./data_bags/bag_name/file`. For example `knife data bag from file users
69
- dan.json` would attempt to load the file `./data_bags/users/dan.json`.
70
-
71
- ## LIST
72
- __knife data bag list__ _(options)_
73
-
74
- * `-w`, `--with-uri`:
75
- Show corresponding URIs
76
-
77
- Lists the data bags that exist on the Chef Server.
78
-
79
- ## SHOW
80
- __knife data bag show BAG [ITEM]__ _(options)_
81
-
82
- * `-s`, `--secret SECRET`:
83
- A secret key used to encrypt the data bag item. See __encryption support__ below.
84
- * `--secret-file SECRET_FILE`:
85
- The path to a file containing the secret key to be used to encrypt
86
- the data bag item.
87
-
88
- Show a specific data bag or an item in a data bag. The output will be
89
- formatted according to the --format option.
90
-
91
- ## ENCRYPTION SUPPORT
92
- Data Bag Items may be encrypted to keep their contents secret. This may
93
- be desireable when storing sensitive information such as database
94
- passwords, API keys, etc.
95
-
96
- Data Bag Item encryption uses the AES-256 CBC symmetric key algorithm.
97
-
98
- __CAVEATS:__ Keys are not encrypted; only values are encrypted. The "id"
99
- of a Data Bag Item is not encrypted, since it is used by Chef Server to
100
- store the item in its database. For example, given the following data bag item:
101
- {"id": "important_passwords", "secret_password": "opensesame"}
102
- The key "secret\_password" will be visible to an evesdropper, but the
103
- value "opensesame" will be protected. Both the key "id" and its value
104
- "important\_passwords" will be visible to an evesdropper.
105
-
106
- Chef Server does not provide a secure mechanism for distributing
107
- encryption keys.
108
-
109
- ## SEE ALSO
110
- __knife-search__(1)
111
-
112
- ## AUTHOR
113
- Chef was written by Adam Jacob <adam@opscode.com> with many contributions from the community.
114
-
115
- ## DOCUMENTATION
116
- This manual page was written by Joshua Timberman <joshua@opscode.com>.
117
- Permission is granted to copy, distribute and / or modify this document under the terms of the Apache 2.0 License.
118
-
119
- ## CHEF
120
- Knife is distributed with Chef. http://wiki.opscode.com/display/chef/Home
121
-
@@ -1,151 +0,0 @@
1
- knife-environment(1) -- Define cookbook policies for the environments in your infrastructure
2
- ========================================
3
-
4
- ## SYNOPSIS
5
-
6
- __knife__ __environment__ _sub-command_ _(options)_
7
-
8
- ## SUBCOMMANDS
9
- Environment subcommands follow a basic create, read, update, delete
10
- (CRUD) pattern. The following subcommands are available:
11
-
12
- ## CREATE
13
- __knife environment create__ _environment_ _(options)_
14
-
15
- * `-d`, `--description DESCRIPTION`:
16
- The value of the description field.
17
-
18
- Create a new environment object on the Chef Server. The envrionment will
19
- be opened in the text editor for editing prior to creation if the -n
20
- option is not present.
21
-
22
- ## DELETE
23
- __knife environment delete__ _environment_ _(options)_
24
-
25
- Destroy an environment on the Chef Server. A prompt for confirmation
26
- will be displayed if the -y options is not given.
27
-
28
- ## EDIT
29
- __knife environment edit__ _environment_ _(options)_
30
-
31
- Fetch _environment_ and display it in the text editor for editing. The
32
- environment will be saved to the Chef Server when the editing session
33
- exits.
34
-
35
- ## FROM FILE
36
- __knife environment from file__ _file_ _(options)_
37
-
38
- Create or update an environment from the JSON or Ruby format _file_. See
39
- __format__ for the proper format of this file.
40
-
41
- ## LIST
42
- __knife environment list__ _(options)_
43
- * `-w`, `--with-uri`:
44
- Show the resource URI for each environment
45
-
46
- ## SHOW
47
- __knife environment show__ _environment_ _(options)_
48
-
49
- ## DESCRIPTION
50
- Environments provide a means to apply policies to hosts in your
51
- infrastructure based on business function. For example, you may have a
52
- separate copy of your infrastructure called "dev" that runs the latest
53
- version of your application and should use the newest versions of your
54
- cookbooks when configuring systems, and a production instance of your
55
- infrastructure where you wish to update code and cookbooks in a more
56
- controlled fashion. In Chef, this function is implemented with
57
- _environments_.
58
-
59
- Environments contain two major components: a set of cookbook version
60
- constraints and environment attributes.
61
-
62
- ## SYNTAX
63
- A cookbook version constraint is comprised of a _cookbook name_ and a
64
- _version constraint_. The _cookbook name_ is the name of a cookbook in
65
- your system, and the _version constraint_ is a String describing the
66
- version(s) of that cookbook allowed in the environment. Only one
67
- _version constraint_ is supported for a given _cookbook name_.
68
-
69
- The exact syntax used to define a cookbook version constraint varies
70
- depending on whether you use the JSON format or the Ruby format. In the
71
- JSON format, the cookbook version constraints for an environment are
72
- represented as a single JSON object, like this:
73
-
74
- {"apache2": ">= 1.5.0"}
75
-
76
- In the Ruby format, the cookbook version contraints for an environment
77
- are represented as a Ruby Hash, like this:
78
-
79
- {"apache2" => ">= 1.5.0"}
80
-
81
- A _version number_ is a String comprised of two or three digits
82
- separated by a dot (.) character, or in other words, strings of the form
83
- "major.minor" or "major.minor.patch". "1.2" and "1.2.3" are examples of
84
- valid version numbers. Version numbers containing more than three digits
85
- or alphabetic characters are not supported.
86
-
87
- A _version constraint_ String is composed of an _operator_ and a
88
- _version number_. The following operators are available:
89
-
90
- * `= VERSION`:
91
- Equality. Only the exact version specified may be used.
92
- * `> VERSION`:
93
- Greater than. Only versions greater than `VERSION` may be used.
94
- * `>= VERSION`:
95
- Greater than or equal to. Only versions equal to VERSION or greater
96
- may be used.
97
- * `< VERSION`:
98
- Less than. Only versions less than VERSION may be used.
99
- * `<= VERSION`:
100
- Less than or equal to. Only versions lesser or equal to VERSION may
101
- be used.
102
- * `~> VERSION`:
103
- Pessimistic greater than. Depending on the number of components in
104
- the given VERSION, the constraint will be optimistic about future
105
- minor or patch revisions only. For example, `~> 1.1` will match any
106
- version less than `2.0` and greater than or equal to `1.1.0`,
107
- whereas `~> 2.0.5` will match any version less than `2.1.0` and
108
- greater than or equal to `2.0.5`.
109
-
110
- ## FORMAT
111
- The JSON format of an envioronment is as follows:
112
-
113
- {
114
- "name": "dev",
115
- "description": "The development environment",
116
- "cookbook_versions": {
117
- "couchdb": "= 11.0.0"
118
- },
119
- "json_class": "Chef::Environment",
120
- "chef_type": "environment",
121
- "default_attributes": {
122
- "apache2": { "listen_ports": [ "80", "443" ] }
123
- },
124
- "override_attributes": {
125
- "aws_s3_bucket": "production"
126
- }
127
- }
128
-
129
- The Ruby format of an environment is as follows:
130
-
131
- name "dev"
132
- description "The development environment"
133
- cookbook_versions "couchdb" => "= 11.0.0"
134
- default_attributes "apache2" => { "listen_ports" => [ "80", "443" ] }
135
- override_attributes "aws_s3_bucket" => "production"
136
-
137
-
138
- ## SEE ALSO
139
- __knife-node(1)__ __knife-cookbook(1)__ __knife-role(1)__
140
- <http://wiki.opscode.com/display/chef/Environments>
141
- <http://wiki.opscode.com/display/chef/Version+Constraints>
142
-
143
- ## AUTHOR
144
- Chef was written by Adam Jacob <adam@opscode.com> with many contributions from the community.
145
-
146
- ## DOCUMENTATION
147
- This manual page was written by Daniel DeLeo <dan@opscode.com>.
148
- Permission is granted to copy, distribute and / or modify this document under the terms of the Apache 2.0 License.
149
-
150
- ## CHEF
151
- Knife is distributed with Chef. <http://wiki.opscode.com/display/chef/Home>
@@ -1,42 +0,0 @@
1
- knife-exec(1) -- Run user scripts using the Chef API DSL
2
- ========================================
3
-
4
- ## SYNOPSIS
5
-
6
- __knife__ __exec__ _(options)_
7
-
8
- * `-E`, `--exec CODE`:
9
- Provide a snippet of code to evaluate on the command line
10
-
11
- ## DESCRIPTION
12
-
13
- `knife exec` runs arbitrary ruby scripts in a context similar to that
14
- of the chef-shell(1) DSL. See the chef-shell documentation for a
15
- description of the commands available.
16
-
17
- ## EXAMPLES
18
-
19
- * Make an API call against an arbitrary endpoint:
20
- knife exec -E 'api.get("nodes/fluke.localdomain/cookbooks")'
21
- => list of cookbooks for the node _fluke.localdomain_
22
- * Remove the role _obsolete_ from all nodes:
23
- knife exec -E 'nodes.transform(:all){|n| n.run\_list.delete("role[obsolete]")}'
24
- * Generate the expanded run list for hosts in the `webserver` role:
25
- knife exec -E 'nodes.find(:roles => "webserver") {|n| n.expand!; n[:recipes]}'
26
-
27
- ## SEE ALSO
28
-
29
- __chef-shell(1)__
30
-
31
- ## AUTHOR
32
-
33
- Chef was written by Adam Jacob <adam@opscode.com> with many contributions from the community.
34
-
35
- ## DOCUMENTATION
36
-
37
- This manual page was written by Joshua Timberman <joshua@opscode.com>.
38
- Permission is granted to copy, distribute and / or modify this document under the terms of the Apache 2.0 License.
39
-
40
- ## CHEF
41
-
42
- Knife is distributed with Chef. <http://wiki.opscode.com/display/chef/Home>
@@ -1,30 +0,0 @@
1
- knife-index(1) -- Rebuild the search index on a Chef Server
2
- ========================================
3
-
4
- ## SYNOPSIS
5
-
6
- __knife__ __index rebuild__ _(options)_
7
-
8
- * `-y`, `--yes`:
9
- don't bother to ask if I'm sure
10
-
11
- ## DESCRIPTION
12
- Rebuilds all the search indexes on the server. This is accomplished by
13
- deleting all objects from the search index, and then forwarding each
14
- item in the database to __chef-expander__(8) via __rabbitmq-server__(1).
15
- Depending on the number of objects in the database, it may take some
16
- time for all objects to be indexed and available for search.
17
-
18
- ## SEE ALSO
19
- __knife-search__(1)
20
-
21
- ## AUTHOR
22
- Chef was written by Adam Jacob <adam@opscode.com> with many contributions from the community.
23
-
24
- ## DOCUMENTATION
25
- This manual page was written by Joshua Timberman <joshua@opscode.com>.
26
- Permission is granted to copy, distribute and / or modify this document under the terms of the Apache 2.0 License.
27
-
28
- ## CHEF
29
- Knife is distributed with Chef. <http://wiki.opscode.com/display/chef/Home>
30
-
@@ -1,130 +0,0 @@
1
- knife-node(1) -- Manage the hosts in your infrastructure
2
- ========================================
3
-
4
- ## SYNOPSIS
5
-
6
- __knife__ __node__ _sub-command_ _(options)_
7
-
8
- ## DESCRIPTION
9
- Nodes are data structures that represent hosts configured with Chef.
10
- Nodes have a __name__, a String that uniquely identifies the node,
11
- __attributes__, a nested Hash of properties that describe how the host
12
- should be configured, a __chef\_environment__, a String representing the
13
- environment to which the node belongs, and a __run\_list__, an ordered
14
- list of __recipes__ or __roles__ that chef-client should apply when
15
- configuring a host.
16
-
17
- When a host communicates with a Chef Server, it authenticates using its
18
- __node\_name__ for identification and signs its reqests with a private
19
- key. The Server validates the request by looking up a __client__ object
20
- with a name identical to the __node\_name__ submitted with the request
21
- and verifes the signature using the public key for that __client__
22
- object. __NOTE__ that the __client__ is a different object in the
23
- system. It is associated with a node by virtue of having a matching
24
- name.
25
-
26
- By default __chef-client__(8) will create a node using the FQDN of the
27
- host for the node name, though this may be overridden by configuration
28
- settings.
29
-
30
- ## NODE SUB-COMMANDS
31
- The following `node` subcommands are available:
32
-
33
- ## BULK DELETE
34
- __knife node bulk delete__ _regex_ _(options)_
35
-
36
- Deletes nodes for which the name matches the regular expression _regex_
37
- on the Chef Server. The regular expression should be given in quotes,
38
- and should not be surrounded with forward slashes (as is typical of
39
- regular expression literals in scripting languages).
40
-
41
- ## CREATE
42
- __knife node create__ _name_ _(options)_
43
-
44
- Create a new node. Unless the --disable-editing option is given, an empty node
45
- object will be created and displayed in your text editor. If the editor
46
- exits with a successful exit status, the node data will be posted to the
47
- Chef Server to create the node.
48
-
49
- ## DELETE
50
- __knife node delete__ _name_ _(options)_
51
-
52
- Deletes the node identified by _name_ on the Chef Server.
53
-
54
- ## EDIT
55
- __knife node edit__ _name_ _(options)_
56
-
57
- * `-a`, `--all`:
58
- Display all node data in the editor. By default, default, override,
59
- and automatic attributes are not shown.
60
-
61
- Edit the node identified by _name_. Like __knife node create__, the node
62
- will be displayed in your text editor unless the -n option is present.
63
-
64
- ## FROM FILE
65
- __knife node from file__ _file_ _(options)_
66
-
67
- Create a node from a JSON format _file_.
68
-
69
- ## LIST
70
- __knife node list__ _(options)_
71
-
72
- * `-w`, `--with-uri`:
73
- Show corresponding URIs
74
-
75
- List all nodes.
76
-
77
- ## RUN\_LIST ADD
78
- __knife node run_list add__ _name_ _run list item_ _(options)_
79
-
80
- * `-a`, `--after ITEM`:
81
- Place the ENTRY in the run list after ITEM
82
-
83
- Add the _run list item_ to the node's `run_list`. See Run list
84
-
85
- ## RUN\_LIST REMOVE
86
- __knife node run_list remove__ _node name_ _run list item_ _(options)_
87
-
88
- Remove the _run list item_ from the node's `run_list`.
89
-
90
- ## SHOW
91
- __knife node show__ _node name_ _(options)_
92
-
93
- * `-a`, `--attribute [ATTR]`:
94
- Show only one attribute
95
- * `-r`, `--run-list `:
96
- Show only the run list
97
- * `-F`, `--format FORMAT`:
98
- Display the node in a different format.
99
- * `-m`, `--medium`:
100
- Display more, but not all, of the node's data when using the default
101
- _summary_ format
102
-
103
- Displays the node identified by _node name_ on stdout.
104
-
105
- ## RUN LIST ITEM FORMAT
106
- Run list items may be either roles or recipes. When adding a role to a
107
- run list, the correct syntax is "role[ROLE\_NAME]"
108
-
109
- When adding a recipe to a run list, there are several valid formats:
110
-
111
- * Fully Qualified Format:
112
- "recipe[COOKBOOK::RECIPE\_NAME]", for example, "recipe[chef::client]"
113
- * Cookbook Recipe Format:
114
- For brevity, the recipe part of the fully qualified format may be omitted, and recipes specified as "COOKBOOK::RECIPE\_NAME", e.g., "chef::client"
115
- * Default Recipe Format:
116
- When adding the default recipe of a cookbook to a run list, the recipe name may be omitted as well, e.g., "chef::default" may be written as just "chef"
117
-
118
- ## SEE ALSO
119
- __knife-client__(1) __knife-search__(1) __knife-role__(1)
120
-
121
- ## AUTHOR
122
- Chef was written by Adam Jacob <adam@opscode.com> with many contributions from the community.
123
-
124
- ## DOCUMENTATION
125
- This manual page was written by Joshua Timberman <joshua@opscode.com>.
126
- Permission is granted to copy, distribute and / or modify this document under the terms of the Apache 2.0 License.
127
-
128
- ## CHEF
129
- Knife is distributed with Chef. <http://wiki.opscode.com/display/chef/Home>
130
-