puppet 3.1.0.rc1 → 3.1.0.rc2

Sign up to get free protection for your applications and to get access to all the features.

Potentially problematic release.


This version of puppet might be problematic. Click here for more details.

Files changed (127) hide show
  1. data/COMMITTERS.md +185 -0
  2. data/ext/debian/changelog.erb +6 -0
  3. data/ext/debian/puppet-common.manpages +1 -0
  4. data/ext/debian/puppet.default +3 -1
  5. data/ext/debian/puppetmaster.default +6 -3
  6. data/ext/redhat/puppet.spec.erb +16 -5
  7. data/lib/puppet.rb +3 -5
  8. data/lib/puppet/defaults.rb +6 -5
  9. data/lib/puppet/dsl.rb +3 -7
  10. data/lib/puppet/dsl/resource_api.rb +120 -0
  11. data/lib/puppet/dsl/resource_type_api.rb +34 -0
  12. data/lib/puppet/module_tool.rb +23 -11
  13. data/lib/puppet/network/formats.rb +1 -1
  14. data/lib/puppet/node/environment.rb +1 -3
  15. data/lib/puppet/parser/ast/definition.rb +5 -2
  16. data/lib/puppet/parser/ast/hostclass.rb +3 -2
  17. data/lib/puppet/parser/ast/node.rb +5 -2
  18. data/lib/puppet/parser/ast/resourceparam.rb +1 -1
  19. data/lib/puppet/parser/compiler.rb +0 -10
  20. data/lib/puppet/parser/lexer.rb +50 -39
  21. data/lib/puppet/parser/parser_support.rb +29 -11
  22. data/lib/puppet/parser/scope.rb +2 -2
  23. data/lib/puppet/parser/type_loader.rb +7 -31
  24. data/lib/puppet/provider/package/openbsd.rb +16 -2
  25. data/lib/puppet/provider/package/pip.rb +11 -2
  26. data/lib/puppet/provider/package/portage.rb +29 -12
  27. data/lib/puppet/provider/service/launchd.rb +19 -14
  28. data/lib/puppet/provider/service/upstart.rb +1 -1
  29. data/lib/puppet/provider/user/hpux.rb +37 -2
  30. data/lib/puppet/resource.rb +25 -38
  31. data/lib/puppet/resource/type.rb +6 -14
  32. data/lib/puppet/settings.rb +1 -1
  33. data/lib/puppet/ssl/certificate_authority.rb +4 -1
  34. data/lib/puppet/ssl/certificate_request.rb +3 -1
  35. data/lib/puppet/ssl/certificate_signer.rb +22 -0
  36. data/lib/puppet/type.rb +4 -4
  37. data/lib/puppet/util/methodhelper.rb +0 -19
  38. data/lib/puppet/util/rubygems.rb +3 -1
  39. data/lib/puppet/util/selinux.rb +1 -6
  40. data/lib/puppet/version.rb +1 -1
  41. data/man/man5/puppet.conf.5 +81 -95
  42. data/man/man8/extlookup2hiera.8 +23 -0
  43. data/man/man8/puppet-agent.8 +3 -3
  44. data/man/man8/puppet-apply.8 +2 -6
  45. data/man/man8/puppet-ca.8 +6 -7
  46. data/man/man8/puppet-catalog.8 +6 -7
  47. data/man/man8/puppet-cert.8 +4 -4
  48. data/man/man8/puppet-certificate.8 +6 -7
  49. data/man/man8/puppet-certificate_request.8 +6 -7
  50. data/man/man8/puppet-certificate_revocation_list.8 +6 -7
  51. data/man/man8/puppet-config.8 +4 -8
  52. data/man/man8/puppet-describe.8 +1 -1
  53. data/man/man8/puppet-device.8 +1 -1
  54. data/man/man8/puppet-doc.8 +3 -3
  55. data/man/man8/puppet-facts.8 +4 -8
  56. data/man/man8/puppet-file.8 +6 -7
  57. data/man/man8/puppet-filebucket.8 +1 -1
  58. data/man/man8/puppet-help.8 +2 -6
  59. data/man/man8/puppet-inspect.8 +1 -1
  60. data/man/man8/puppet-instrumentation_data.8 +3 -7
  61. data/man/man8/puppet-instrumentation_listener.8 +3 -7
  62. data/man/man8/puppet-instrumentation_probe.8 +3 -7
  63. data/man/man8/puppet-key.8 +6 -7
  64. data/man/man8/puppet-kick.8 +5 -1
  65. data/man/man8/puppet-man.8 +2 -6
  66. data/man/man8/puppet-master.8 +2 -2
  67. data/man/man8/puppet-module.8 +11 -9
  68. data/man/man8/puppet-node.8 +38 -37
  69. data/man/man8/puppet-parser.8 +2 -6
  70. data/man/man8/puppet-plugin.8 +2 -6
  71. data/man/man8/puppet-queue.8 +1 -1
  72. data/man/man8/puppet-report.8 +3 -7
  73. data/man/man8/puppet-resource.8 +1 -1
  74. data/man/man8/puppet-resource_type.8 +3 -7
  75. data/man/man8/puppet-secret_agent.8 +2 -6
  76. data/man/man8/puppet-status.8 +3 -7
  77. data/man/man8/puppet.8 +1 -1
  78. data/spec/integration/parser/ruby_manifest_spec.rb +128 -0
  79. data/spec/lib/puppet_spec/compiler.rb +0 -11
  80. data/spec/spec_helper.rb +3 -4
  81. data/spec/unit/dsl/resource_api_spec.rb +180 -0
  82. data/spec/unit/dsl/resource_type_api_spec.rb +53 -0
  83. data/spec/unit/module_tool_spec.rb +79 -46
  84. data/spec/unit/network/formats_spec.rb +4 -0
  85. data/spec/unit/node/environment_spec.rb +0 -13
  86. data/spec/unit/parser/compiler_spec.rb +0 -26
  87. data/spec/unit/parser/parser_spec.rb +14 -0
  88. data/spec/unit/parser/type_loader_spec.rb +4 -15
  89. data/spec/unit/provider/package/openbsd_spec.rb +148 -35
  90. data/spec/unit/provider/package/pip_spec.rb +49 -25
  91. data/spec/unit/provider/package/portage_spec.rb +65 -0
  92. data/spec/unit/provider/service/launchd_spec.rb +6 -5
  93. data/spec/unit/provider/user/hpux_spec.rb +39 -11
  94. data/spec/unit/provider/user/useradd_spec.rb +14 -14
  95. data/spec/unit/resource/type_spec.rb +7 -49
  96. data/spec/unit/resource_spec.rb +0 -32
  97. data/spec/unit/ssl/certificate_request_spec.rb +18 -0
  98. data/spec/unit/util/rubygems_spec.rb +1 -1
  99. data/spec/unit/util/selinux_spec.rb +0 -2
  100. metadata +17 -50
  101. data/lib/puppet/dsl/actions.rb +0 -283
  102. data/lib/puppet/dsl/blank_slate.rb +0 -55
  103. data/lib/puppet/dsl/context.rb +0 -393
  104. data/lib/puppet/dsl/parser.rb +0 -57
  105. data/lib/puppet/dsl/resource_decorator.rb +0 -56
  106. data/lib/puppet/dsl/resource_reference.rb +0 -95
  107. data/lib/puppet/dsl/type_reference.rb +0 -102
  108. data/lib/puppet/util/manifest_filetype_helper.rb +0 -22
  109. data/spec/integration/dsl/classes_spec.rb +0 -191
  110. data/spec/integration/dsl/defaults_spec.rb +0 -38
  111. data/spec/integration/dsl/definitions_spec.rb +0 -73
  112. data/spec/integration/dsl/functions_spec.rb +0 -95
  113. data/spec/integration/dsl/nodes_spec.rb +0 -96
  114. data/spec/integration/dsl/params_spec.rb +0 -146
  115. data/spec/integration/dsl/relationships_spec.rb +0 -46
  116. data/spec/integration/dsl/resources_spec.rb +0 -202
  117. data/spec/integration/dsl/type_loading_spec.rb +0 -64
  118. data/spec/lib/matchers/catalog.rb +0 -50
  119. data/spec/lib/puppet_spec/dsl.rb +0 -29
  120. data/spec/unit/dsl/actions_spec.rb +0 -402
  121. data/spec/unit/dsl/blank_slate_spec.rb +0 -27
  122. data/spec/unit/dsl/context_spec.rb +0 -678
  123. data/spec/unit/dsl/parser_spec.rb +0 -56
  124. data/spec/unit/dsl/resource_decorator_spec.rb +0 -94
  125. data/spec/unit/dsl/resource_reference_spec.rb +0 -150
  126. data/spec/unit/dsl/type_reference_spec.rb +0 -164
  127. data/spec/unit/util/manifest_filetype_helper_spec.rb +0 -29
@@ -1,7 +1,7 @@
1
1
  .\" generated with Ronn/v0.7.3
2
2
  .\" http://github.com/rtomayko/ronn/tree/0.7.3
3
3
  .
4
- .TH "PUPPET\-FILE" "8" "May 2012" "Puppet Labs, LLC" "Puppet manual"
4
+ .TH "PUPPET\-FILE" "8" "January 2013" "Puppet Labs, LLC" "Puppet manual"
5
5
  .
6
6
  .SH "NAME"
7
7
  \fBpuppet\-file\fR \- Retrieve and store files in a filebucket
@@ -13,16 +13,12 @@ puppet file \fIaction\fR [\-\-terminus TERMINUS] [\-\-extra HASH]
13
13
  This subcommand interacts with objects stored in a local or remote filebucket\. File objects are accessed by their MD5 sum; see the examples for the relevant syntax\.
14
14
  .
15
15
  .SH "OPTIONS"
16
- Note that any configuration parameter that\'s valid in the configuration file is also a valid long argument, although it may or may not be relevant to the present action\. For example, \fBserver\fR is a valid configuration parameter, so you can specify \fB\-\-server <servername>\fR as an argument\.
16
+ Note that any configuration parameter that\'s valid in the configuration file is also a valid long argument, although it may or may not be relevant to the present action\. For example, \fBserver\fR and \fBrun_mode\fR are valid configuration parameters, so you can specify \fB\-\-server <servername>\fR, or \fB\-\-run_mode <runmode>\fR as an argument\.
17
17
  .
18
18
  .P
19
19
  See the configuration file documentation at \fIhttp://docs\.puppetlabs\.com/references/stable/configuration\.html\fR for the full list of acceptable parameters\. A commented list of all configuration options can also be generated by running puppet with \fB\-\-genconfig\fR\.
20
20
  .
21
21
  .TP
22
- \-\-mode MODE
23
- The run mode to use for the current action\. Valid modes are \fBuser\fR, \fBagent\fR, and \fBmaster\fR\.
24
- .
25
- .TP
26
22
  \-\-render\-as FORMAT
27
23
  The format in which to render output\. The most common formats are \fBjson\fR, \fBs\fR (string), \fByaml\fR, and \fBconsole\fR, but other options such as \fBdot\fR are sometimes available\.
28
24
  .
@@ -115,7 +111,7 @@ puppet file info [\-\-terminus TERMINUS] [\-\-extra HASH]
115
111
  \fBDESCRIPTION\fR
116
112
  .
117
113
  .IP
118
- Prints the default terminus class for this subcommand\. Note that different run modes may have different default termini; when in doubt, specify the run mode with the \'\-\-mode\' option\.
114
+ Prints the default terminus class for this subcommand\. Note that different run modes may have different default termini; when in doubt, specify the run mode with the \'\-\-run_mode\' option\.
119
115
  .
120
116
  .TP
121
117
  \fBsave\fR \- API only: create or overwrite an object\.
@@ -210,6 +206,9 @@ This subcommand is an indirector face, which exposes \fBfind\fR, \fBsearch\fR, \
210
206
  .IP "\(bu" 4
211
207
  \fBrest\fR
212
208
  .
209
+ .IP "\(bu" 4
210
+ \fBselector\fR
211
+ .
213
212
  .IP "" 0
214
213
  .
215
214
  .SH "COPYRIGHT AND LICENSE"
@@ -1,7 +1,7 @@
1
1
  .\" generated with Ronn/v0.7.3
2
2
  .\" http://github.com/rtomayko/ronn/tree/0.7.3
3
3
  .
4
- .TH "PUPPET\-FILEBUCKET" "8" "May 2012" "Puppet Labs, LLC" "Puppet manual"
4
+ .TH "PUPPET\-FILEBUCKET" "8" "January 2013" "Puppet Labs, LLC" "Puppet manual"
5
5
  .
6
6
  .SH "NAME"
7
7
  \fBpuppet\-filebucket\fR \- Store and retrieve files in a filebucket
@@ -1,7 +1,7 @@
1
1
  .\" generated with Ronn/v0.7.3
2
2
  .\" http://github.com/rtomayko/ronn/tree/0.7.3
3
3
  .
4
- .TH "PUPPET\-HELP" "8" "May 2012" "Puppet Labs, LLC" "Puppet manual"
4
+ .TH "PUPPET\-HELP" "8" "January 2013" "Puppet Labs, LLC" "Puppet manual"
5
5
  .
6
6
  .SH "NAME"
7
7
  \fBpuppet\-help\fR \- Display Puppet help\.
@@ -10,16 +10,12 @@
10
10
  puppet help \fIaction\fR
11
11
  .
12
12
  .SH "OPTIONS"
13
- Note that any configuration parameter that\'s valid in the configuration file is also a valid long argument, although it may or may not be relevant to the present action\. For example, \fBserver\fR is a valid configuration parameter, so you can specify \fB\-\-server <servername>\fR as an argument\.
13
+ Note that any configuration parameter that\'s valid in the configuration file is also a valid long argument, although it may or may not be relevant to the present action\. For example, \fBserver\fR and \fBrun_mode\fR are valid configuration parameters, so you can specify \fB\-\-server <servername>\fR, or \fB\-\-run_mode <runmode>\fR as an argument\.
14
14
  .
15
15
  .P
16
16
  See the configuration file documentation at \fIhttp://docs\.puppetlabs\.com/references/stable/configuration\.html\fR for the full list of acceptable parameters\. A commented list of all configuration options can also be generated by running puppet with \fB\-\-genconfig\fR\.
17
17
  .
18
18
  .TP
19
- \-\-mode MODE
20
- The run mode to use for the current action\. Valid modes are \fBuser\fR, \fBagent\fR, and \fBmaster\fR\.
21
- .
22
- .TP
23
19
  \-\-render\-as FORMAT
24
20
  The format in which to render output\. The most common formats are \fBjson\fR, \fBs\fR (string), \fByaml\fR, and \fBconsole\fR, but other options such as \fBdot\fR are sometimes available\.
25
21
  .
@@ -1,7 +1,7 @@
1
1
  .\" generated with Ronn/v0.7.3
2
2
  .\" http://github.com/rtomayko/ronn/tree/0.7.3
3
3
  .
4
- .TH "PUPPET\-INSPECT" "8" "May 2012" "Puppet Labs, LLC" "Puppet manual"
4
+ .TH "PUPPET\-INSPECT" "8" "January 2013" "Puppet Labs, LLC" "Puppet manual"
5
5
  .
6
6
  .SH "NAME"
7
7
  \fBpuppet\-inspect\fR \- Send an inspection report
@@ -1,7 +1,7 @@
1
1
  .\" generated with Ronn/v0.7.3
2
2
  .\" http://github.com/rtomayko/ronn/tree/0.7.3
3
3
  .
4
- .TH "PUPPET\-INSTRUMENTATION_DATA" "8" "May 2012" "Puppet Labs, LLC" "Puppet manual"
4
+ .TH "PUPPET\-INSTRUMENTATION_DATA" "8" "January 2013" "Puppet Labs, LLC" "Puppet manual"
5
5
  .
6
6
  .SH "NAME"
7
7
  \fBpuppet\-instrumentation_data\fR \- Manage instrumentation listener accumulated data\.
@@ -13,16 +13,12 @@ puppet instrumentation_data \fIaction\fR [\-\-terminus TERMINUS] [\-\-extra HASH
13
13
  This subcommand allows to retrieve the various listener data\.
14
14
  .
15
15
  .SH "OPTIONS"
16
- Note that any configuration parameter that\'s valid in the configuration file is also a valid long argument, although it may or may not be relevant to the present action\. For example, \fBserver\fR is a valid configuration parameter, so you can specify \fB\-\-server <servername>\fR as an argument\.
16
+ Note that any configuration parameter that\'s valid in the configuration file is also a valid long argument, although it may or may not be relevant to the present action\. For example, \fBserver\fR and \fBrun_mode\fR are valid configuration parameters, so you can specify \fB\-\-server <servername>\fR, or \fB\-\-run_mode <runmode>\fR as an argument\.
17
17
  .
18
18
  .P
19
19
  See the configuration file documentation at \fIhttp://docs\.puppetlabs\.com/references/stable/configuration\.html\fR for the full list of acceptable parameters\. A commented list of all configuration options can also be generated by running puppet with \fB\-\-genconfig\fR\.
20
20
  .
21
21
  .TP
22
- \-\-mode MODE
23
- The run mode to use for the current action\. Valid modes are \fBuser\fR, \fBagent\fR, and \fBmaster\fR\.
24
- .
25
- .TP
26
22
  \-\-render\-as FORMAT
27
23
  The format in which to render output\. The most common formats are \fBjson\fR, \fBs\fR (string), \fByaml\fR, and \fBconsole\fR, but other options such as \fBdot\fR are sometimes available\.
28
24
  .
@@ -93,7 +89,7 @@ puppet instrumentation_data info [\-\-terminus TERMINUS] [\-\-extra HASH]
93
89
  \fBDESCRIPTION\fR
94
90
  .
95
91
  .IP
96
- Prints the default terminus class for this subcommand\. Note that different run modes may have different default termini; when in doubt, specify the run mode with the \'\-\-mode\' option\.
92
+ Prints the default terminus class for this subcommand\. Note that different run modes may have different default termini; when in doubt, specify the run mode with the \'\-\-run_mode\' option\.
97
93
  .
98
94
  .TP
99
95
  \fBsave\fR \- Invalid for this subcommand\.
@@ -1,7 +1,7 @@
1
1
  .\" generated with Ronn/v0.7.3
2
2
  .\" http://github.com/rtomayko/ronn/tree/0.7.3
3
3
  .
4
- .TH "PUPPET\-INSTRUMENTATION_LISTENER" "8" "May 2012" "Puppet Labs, LLC" "Puppet manual"
4
+ .TH "PUPPET\-INSTRUMENTATION_LISTENER" "8" "January 2013" "Puppet Labs, LLC" "Puppet manual"
5
5
  .
6
6
  .SH "NAME"
7
7
  \fBpuppet\-instrumentation_listener\fR \- Manage instrumentation listeners\.
@@ -13,16 +13,12 @@ puppet instrumentation_listener \fIaction\fR [\-\-terminus TERMINUS] [\-\-extra
13
13
  This subcommand enables/disables or list instrumentation listeners\.
14
14
  .
15
15
  .SH "OPTIONS"
16
- Note that any configuration parameter that\'s valid in the configuration file is also a valid long argument, although it may or may not be relevant to the present action\. For example, \fBserver\fR is a valid configuration parameter, so you can specify \fB\-\-server <servername>\fR as an argument\.
16
+ Note that any configuration parameter that\'s valid in the configuration file is also a valid long argument, although it may or may not be relevant to the present action\. For example, \fBserver\fR and \fBrun_mode\fR are valid configuration parameters, so you can specify \fB\-\-server <servername>\fR, or \fB\-\-run_mode <runmode>\fR as an argument\.
17
17
  .
18
18
  .P
19
19
  See the configuration file documentation at \fIhttp://docs\.puppetlabs\.com/references/stable/configuration\.html\fR for the full list of acceptable parameters\. A commented list of all configuration options can also be generated by running puppet with \fB\-\-genconfig\fR\.
20
20
  .
21
21
  .TP
22
- \-\-mode MODE
23
- The run mode to use for the current action\. Valid modes are \fBuser\fR, \fBagent\fR, and \fBmaster\fR\.
24
- .
25
- .TP
26
22
  \-\-render\-as FORMAT
27
23
  The format in which to render output\. The most common formats are \fBjson\fR, \fBs\fR (string), \fByaml\fR, and \fBconsole\fR, but other options such as \fBdot\fR are sometimes available\.
28
24
  .
@@ -131,7 +127,7 @@ puppet instrumentation_listener info [\-\-terminus TERMINUS] [\-\-extra HASH]
131
127
  \fBDESCRIPTION\fR
132
128
  .
133
129
  .IP
134
- Prints the default terminus class for this subcommand\. Note that different run modes may have different default termini; when in doubt, specify the run mode with the \'\-\-mode\' option\.
130
+ Prints the default terminus class for this subcommand\. Note that different run modes may have different default termini; when in doubt, specify the run mode with the \'\-\-run_mode\' option\.
135
131
  .
136
132
  .TP
137
133
  \fBsave\fR \- API only: modify an instrumentation listener status\.
@@ -1,7 +1,7 @@
1
1
  .\" generated with Ronn/v0.7.3
2
2
  .\" http://github.com/rtomayko/ronn/tree/0.7.3
3
3
  .
4
- .TH "PUPPET\-INSTRUMENTATION_PROBE" "8" "May 2012" "Puppet Labs, LLC" "Puppet manual"
4
+ .TH "PUPPET\-INSTRUMENTATION_PROBE" "8" "January 2013" "Puppet Labs, LLC" "Puppet manual"
5
5
  .
6
6
  .SH "NAME"
7
7
  \fBpuppet\-instrumentation_probe\fR \- Manage instrumentation probes\.
@@ -13,16 +13,12 @@ puppet instrumentation_probe \fIaction\fR [\-\-terminus TERMINUS] [\-\-extra HAS
13
13
  This subcommand enables/disables or list instrumentation listeners\.
14
14
  .
15
15
  .SH "OPTIONS"
16
- Note that any configuration parameter that\'s valid in the configuration file is also a valid long argument, although it may or may not be relevant to the present action\. For example, \fBserver\fR is a valid configuration parameter, so you can specify \fB\-\-server <servername>\fR as an argument\.
16
+ Note that any configuration parameter that\'s valid in the configuration file is also a valid long argument, although it may or may not be relevant to the present action\. For example, \fBserver\fR and \fBrun_mode\fR are valid configuration parameters, so you can specify \fB\-\-server <servername>\fR, or \fB\-\-run_mode <runmode>\fR as an argument\.
17
17
  .
18
18
  .P
19
19
  See the configuration file documentation at \fIhttp://docs\.puppetlabs\.com/references/stable/configuration\.html\fR for the full list of acceptable parameters\. A commented list of all configuration options can also be generated by running puppet with \fB\-\-genconfig\fR\.
20
20
  .
21
21
  .TP
22
- \-\-mode MODE
23
- The run mode to use for the current action\. Valid modes are \fBuser\fR, \fBagent\fR, and \fBmaster\fR\.
24
- .
25
- .TP
26
22
  \-\-render\-as FORMAT
27
23
  The format in which to render output\. The most common formats are \fBjson\fR, \fBs\fR (string), \fByaml\fR, and \fBconsole\fR, but other options such as \fBdot\fR are sometimes available\.
28
24
  .
@@ -125,7 +121,7 @@ puppet instrumentation_probe info [\-\-terminus TERMINUS] [\-\-extra HASH]
125
121
  \fBDESCRIPTION\fR
126
122
  .
127
123
  .IP
128
- Prints the default terminus class for this subcommand\. Note that different run modes may have different default termini; when in doubt, specify the run mode with the \'\-\-mode\' option\.
124
+ Prints the default terminus class for this subcommand\. Note that different run modes may have different default termini; when in doubt, specify the run mode with the \'\-\-run_mode\' option\.
129
125
  .
130
126
  .TP
131
127
  \fBsave\fR \- API only: enable all instrumentation probes\.
@@ -1,7 +1,7 @@
1
1
  .\" generated with Ronn/v0.7.3
2
2
  .\" http://github.com/rtomayko/ronn/tree/0.7.3
3
3
  .
4
- .TH "PUPPET\-KEY" "8" "May 2012" "Puppet Labs, LLC" "Puppet manual"
4
+ .TH "PUPPET\-KEY" "8" "January 2013" "Puppet Labs, LLC" "Puppet manual"
5
5
  .
6
6
  .SH "NAME"
7
7
  \fBpuppet\-key\fR \- Create, save, and remove certificate keys\.
@@ -13,16 +13,12 @@ puppet key \fIaction\fR [\-\-terminus TERMINUS] [\-\-extra HASH]
13
13
  This subcommand manages certificate private keys\. Keys are created automatically by puppet agent and when certificate requests are generated with \'puppet certificate generate\'; it should not be necessary to use this subcommand directly\.
14
14
  .
15
15
  .SH "OPTIONS"
16
- Note that any configuration parameter that\'s valid in the configuration file is also a valid long argument, although it may or may not be relevant to the present action\. For example, \fBserver\fR is a valid configuration parameter, so you can specify \fB\-\-server <servername>\fR as an argument\.
16
+ Note that any configuration parameter that\'s valid in the configuration file is also a valid long argument, although it may or may not be relevant to the present action\. For example, \fBserver\fR and \fBrun_mode\fR are valid configuration parameters, so you can specify \fB\-\-server <servername>\fR, or \fB\-\-run_mode <runmode>\fR as an argument\.
17
17
  .
18
18
  .P
19
19
  See the configuration file documentation at \fIhttp://docs\.puppetlabs\.com/references/stable/configuration\.html\fR for the full list of acceptable parameters\. A commented list of all configuration options can also be generated by running puppet with \fB\-\-genconfig\fR\.
20
20
  .
21
21
  .TP
22
- \-\-mode MODE
23
- The run mode to use for the current action\. Valid modes are \fBuser\fR, \fBagent\fR, and \fBmaster\fR\.
24
- .
25
- .TP
26
22
  \-\-render\-as FORMAT
27
23
  The format in which to render output\. The most common formats are \fBjson\fR, \fBs\fR (string), \fByaml\fR, and \fBconsole\fR, but other options such as \fBdot\fR are sometimes available\.
28
24
  .
@@ -87,7 +83,7 @@ puppet key info [\-\-terminus TERMINUS] [\-\-extra HASH]
87
83
  \fBDESCRIPTION\fR
88
84
  .
89
85
  .IP
90
- Prints the default terminus class for this subcommand\. Note that different run modes may have different default termini; when in doubt, specify the run mode with the \'\-\-mode\' option\.
86
+ Prints the default terminus class for this subcommand\. Note that different run modes may have different default termini; when in doubt, specify the run mode with the \'\-\-run_mode\' option\.
91
87
  .
92
88
  .TP
93
89
  \fBsave\fR \- API only: create or overwrite an object\.
@@ -122,6 +118,9 @@ This subcommand is an indirector face, which exposes \fBfind\fR, \fBsearch\fR, \
122
118
  \fBca\fR
123
119
  .
124
120
  .IP "\(bu" 4
121
+ \fBdisabled_ca\fR
122
+ .
123
+ .IP "\(bu" 4
125
124
  \fBfile\fR
126
125
  .
127
126
  .IP "" 0
@@ -1,7 +1,7 @@
1
1
  .\" generated with Ronn/v0.7.3
2
2
  .\" http://github.com/rtomayko/ronn/tree/0.7.3
3
3
  .
4
- .TH "PUPPET\-KICK" "8" "May 2012" "Puppet Labs, LLC" "Puppet manual"
4
+ .TH "PUPPET\-KICK" "8" "January 2013" "Puppet Labs, LLC" "Puppet manual"
5
5
  .
6
6
  .SH "NAME"
7
7
  \fBpuppet\-kick\fR \- Remotely control puppet agent
@@ -101,6 +101,10 @@ Whether the client should ignore schedules when running its configuration\. This
101
101
  How parallel to make the connections\. Parallelization is provided by forking for each client to which to connect\. The default is 1, meaning serial execution\.
102
102
  .
103
103
  .TP
104
+ \-\-puppetport
105
+ Use the specified TCP port to connect to agents\. Defaults to 8139\.
106
+ .
107
+ .TP
104
108
  \-\-tag
105
109
  Specify a tag for selecting the objects to apply\. Does not work with the \-\-test option\.
106
110
  .
@@ -1,7 +1,7 @@
1
1
  .\" generated with Ronn/v0.7.3
2
2
  .\" http://github.com/rtomayko/ronn/tree/0.7.3
3
3
  .
4
- .TH "PUPPET\-MAN" "8" "May 2012" "Puppet Labs, LLC" "Puppet manual"
4
+ .TH "PUPPET\-MAN" "8" "January 2013" "Puppet Labs, LLC" "Puppet manual"
5
5
  .
6
6
  .SH "NAME"
7
7
  \fBpuppet\-man\fR \- Display Puppet manual pages\.
@@ -13,16 +13,12 @@ puppet man \fIaction\fR
13
13
  This subcommand displays manual pages for all Puppet subcommands\. If the \fBronn\fR gem (\fIhttps://github\.com/rtomayko/ronn/\fR) is installed on your system, puppet man will display fully\-formated man pages\. If \fBronn\fR is not available, puppet man will display the raw (but human\-readable) source text in a pager\.
14
14
  .
15
15
  .SH "OPTIONS"
16
- Note that any configuration parameter that\'s valid in the configuration file is also a valid long argument, although it may or may not be relevant to the present action\. For example, \fBserver\fR is a valid configuration parameter, so you can specify \fB\-\-server <servername>\fR as an argument\.
16
+ Note that any configuration parameter that\'s valid in the configuration file is also a valid long argument, although it may or may not be relevant to the present action\. For example, \fBserver\fR and \fBrun_mode\fR are valid configuration parameters, so you can specify \fB\-\-server <servername>\fR, or \fB\-\-run_mode <runmode>\fR as an argument\.
17
17
  .
18
18
  .P
19
19
  See the configuration file documentation at \fIhttp://docs\.puppetlabs\.com/references/stable/configuration\.html\fR for the full list of acceptable parameters\. A commented list of all configuration options can also be generated by running puppet with \fB\-\-genconfig\fR\.
20
20
  .
21
21
  .TP
22
- \-\-mode MODE
23
- The run mode to use for the current action\. Valid modes are \fBuser\fR, \fBagent\fR, and \fBmaster\fR\.
24
- .
25
- .TP
26
22
  \-\-render\-as FORMAT
27
23
  The format in which to render output\. The most common formats are \fBjson\fR, \fBs\fR (string), \fByaml\fR, and \fBconsole\fR, but other options such as \fBdot\fR are sometimes available\.
28
24
  .
@@ -1,7 +1,7 @@
1
1
  .\" generated with Ronn/v0.7.3
2
2
  .\" http://github.com/rtomayko/ronn/tree/0.7.3
3
3
  .
4
- .TH "PUPPET\-MASTER" "8" "May 2012" "Puppet Labs, LLC" "Puppet manual"
4
+ .TH "PUPPET\-MASTER" "8" "January 2013" "Puppet Labs, LLC" "Puppet manual"
5
5
  .
6
6
  .SH "NAME"
7
7
  \fBpuppet\-master\fR \- The puppet master daemon
@@ -75,4 +75,4 @@ Close file descriptors for log files and reopen them\. Used with logrotate\.
75
75
  Luke Kanies
76
76
  .
77
77
  .SH "COPYRIGHT"
78
- Copyright (c) 2011 Puppet Labs, LLC Licensed under the Apache 2\.0 License
78
+ Copyright (c) 2012 Puppet Labs, LLC Licensed under the Apache 2\.0 License
@@ -1,7 +1,7 @@
1
1
  .\" generated with Ronn/v0.7.3
2
2
  .\" http://github.com/rtomayko/ronn/tree/0.7.3
3
3
  .
4
- .TH "PUPPET\-MODULE" "8" "May 2012" "Puppet Labs, LLC" "Puppet manual"
4
+ .TH "PUPPET\-MODULE" "8" "January 2013" "Puppet Labs, LLC" "Puppet manual"
5
5
  .
6
6
  .SH "NAME"
7
7
  \fBpuppet\-module\fR \- Creates, installs and searches for modules on the Puppet Forge\.
@@ -13,16 +13,12 @@ puppet module \fIaction\fR [\-\-environment production ] [\-\-modulepath $confdi
13
13
  This subcommand can find, install, and manage modules from the Puppet Forge, a repository of user\-contributed Puppet code\. It can also generate empty modules, and prepare locally developed modules for release on the Forge\.
14
14
  .
15
15
  .SH "OPTIONS"
16
- Note that any configuration parameter that\'s valid in the configuration file is also a valid long argument, although it may or may not be relevant to the present action\. For example, \fBserver\fR is a valid configuration parameter, so you can specify \fB\-\-server <servername>\fR as an argument\.
16
+ Note that any configuration parameter that\'s valid in the configuration file is also a valid long argument, although it may or may not be relevant to the present action\. For example, \fBserver\fR and \fBrun_mode\fR are valid configuration parameters, so you can specify \fB\-\-server <servername>\fR, or \fB\-\-run_mode <runmode>\fR as an argument\.
17
17
  .
18
18
  .P
19
19
  See the configuration file documentation at \fIhttp://docs\.puppetlabs\.com/references/stable/configuration\.html\fR for the full list of acceptable parameters\. A commented list of all configuration options can also be generated by running puppet with \fB\-\-genconfig\fR\.
20
20
  .
21
21
  .TP
22
- \-\-mode MODE
23
- The run mode to use for the current action\. Valid modes are \fBuser\fR, \fBagent\fR, and \fBmaster\fR\.
24
- .
25
- .TP
26
22
  \-\-render\-as FORMAT
27
23
  The format in which to render output\. The most common formats are \fBjson\fR, \fBs\fR (string), \fByaml\fR, and \fBconsole\fR, but other options such as \fBdot\fR are sometimes available\.
28
24
  .
@@ -49,7 +45,7 @@ The search path for modules, as a list of directories separated by the system pa
49
45
  \fBSYNOPSIS\fR
50
46
  .
51
47
  .IP
52
- puppet module build \fIpath\fR
48
+ puppet module build [\fIpath\fR]
53
49
  .
54
50
  .IP
55
51
  \fBDESCRIPTION\fR
@@ -124,7 +120,7 @@ puppet module install [\-\-force | \-f] [\-\-target\-dir DIR | \-i DIR] [\-\-ign
124
120
  Installs a module from the Puppet Forge or from a release archive file\.
125
121
  .
126
122
  .IP
127
- The specified module will be installed into the directory specified with the \fB\-\-target\-dir\fR option, which defaults to /Users/matthaus/\.puppet/modules\.
123
+ The specified module will be installed into the directory specified with the \fB\-\-target\-dir\fR option, which defaults to /Users/josh/\.puppet/modules\.
128
124
  .
129
125
  .IP
130
126
  \fBOPTIONS\fR \fI\-\-force\fR | \fI\-f\fR \- Force overwrite of existing module, if any\.
@@ -251,7 +247,13 @@ Hash
251
247
  Build a module release:
252
248
  .
253
249
  .P
254
- $ puppet module build puppetlabs\-apache notice: Building /Users/kelseyhightower/puppetlabs\-apache for release puppetlabs\-apache/pkg/puppetlabs\-apache\-0\.0\.1\.tar\.gz
250
+ $ puppet module build puppetlabs\-apache notice: Building /Users/kelseyhightower/puppetlabs\-apache for release Module built: /Users/kelseyhightower/puppetlabs\-apache/pkg/puppetlabs\-apache\-0\.0\.1\.tar\.gz
251
+ .
252
+ .P
253
+ Build the module in the current working directory:
254
+ .
255
+ .P
256
+ $ cd /Users/kelseyhightower/puppetlabs\-apache $ puppet module build notice: Building /Users/kelseyhightower/puppetlabs\-apache for release Module built: /Users/kelseyhightower/puppetlabs\-apache/pkg/puppetlabs\-apache\-0\.0\.1\.tar\.gz
255
257
  .
256
258
  .P
257
259
  \fBchanges\fR
@@ -1,7 +1,7 @@
1
1
  .\" generated with Ronn/v0.7.3
2
2
  .\" http://github.com/rtomayko/ronn/tree/0.7.3
3
3
  .
4
- .TH "PUPPET\-NODE" "8" "May 2012" "Puppet Labs, LLC" "Puppet manual"
4
+ .TH "PUPPET\-NODE" "8" "January 2013" "Puppet Labs, LLC" "Puppet manual"
5
5
  .
6
6
  .SH "NAME"
7
7
  \fBpuppet\-node\fR \- View and manage node definitions\.
@@ -13,16 +13,12 @@ puppet node \fIaction\fR [\-\-terminus TERMINUS] [\-\-extra HASH]
13
13
  This subcommand interacts with node objects, which are used by Puppet to build a catalog\. A node object consists of the node\'s facts, environment, node parameters (exposed in the parser as top\-scope variables), and classes\.
14
14
  .
15
15
  .SH "OPTIONS"
16
- Note that any configuration parameter that\'s valid in the configuration file is also a valid long argument, although it may or may not be relevant to the present action\. For example, \fBserver\fR is a valid configuration parameter, so you can specify \fB\-\-server <servername>\fR as an argument\.
16
+ Note that any configuration parameter that\'s valid in the configuration file is also a valid long argument, although it may or may not be relevant to the present action\. For example, \fBserver\fR and \fBrun_mode\fR are valid configuration parameters, so you can specify \fB\-\-server <servername>\fR, or \fB\-\-run_mode <runmode>\fR as an argument\.
17
17
  .
18
18
  .P
19
19
  See the configuration file documentation at \fIhttp://docs\.puppetlabs\.com/references/stable/configuration\.html\fR for the full list of acceptable parameters\. A commented list of all configuration options can also be generated by running puppet with \fB\-\-genconfig\fR\.
20
20
  .
21
21
  .TP
22
- \-\-mode MODE
23
- The run mode to use for the current action\. Valid modes are \fBuser\fR, \fBagent\fR, and \fBmaster\fR\.
24
- .
25
- .TP
26
22
  \-\-render\-as FORMAT
27
23
  The format in which to render output\. The most common formats are \fBjson\fR, \fBs\fR (string), \fByaml\fR, and \fBconsole\fR, but other options such as \fBdot\fR are sometimes available\.
28
24
  .
@@ -50,8 +46,9 @@ The terminus for an action is often determined by context, but occasionally need
50
46
  .
51
47
  .SH "ACTIONS"
52
48
  .
53
- .IP "\(bu" 4
54
- \fBclean\fR \- Clean up everything a puppetmaster knows about a node: \fBSYNOPSIS\fR
49
+ .TP
50
+ \fBclean\fR \- Clean up everything a puppetmaster knows about a node\.
51
+ \fBSYNOPSIS\fR
55
52
  .
56
53
  .IP
57
54
  puppet node clean [\-\-terminus TERMINUS] [\-\-extra HASH] [\-\-[no\-]unexport] \fIhost1\fR [\fIhost2\fR \.\.\.]
@@ -60,33 +57,32 @@ puppet node clean [\-\-terminus TERMINUS] [\-\-extra HASH] [\-\-[no\-]unexport]
60
57
  \fBDESCRIPTION\fR
61
58
  .
62
59
  .IP
63
- This includes
60
+ Clean up everything a puppet master knows about a node, including certificates and storeconfigs data\.
64
61
  .
65
- .IP "\(bu" 4
66
- Signed certificates ($vardir/ssl/ca/signed/node\.domain\.pem)
67
- .
68
- .IP "\(bu" 4
69
- Cached facts ($vardir/yaml/facts/node\.domain\.yaml)
62
+ .IP
63
+ The full list of info cleaned by this action is:
70
64
  .
71
- .IP "\(bu" 4
72
- Cached node stuff ($vardir/yaml/node/node\.domain\.yaml)
65
+ .IP
66
+ \fISigned certificates\fR \- ($vardir/ssl/ca/signed/node\.domain\.pem)
73
67
  .
74
- .IP "\(bu" 4
75
- Reports ($vardir/reports/node\.domain)
68
+ .IP
69
+ \fICached facts\fR \- ($vardir/yaml/facts/node\.domain\.yaml)
76
70
  .
77
- .IP "\(bu" 4
78
- Stored configs: it can either remove all data from an host in your storedconfig database, or with \-\-unexport turn every exported resource supporting ensure to absent so that any other host checking out their config can remove those exported configurations\.
71
+ .IP
72
+ \fICached node objects\fR \- ($vardir/yaml/node/node\.domain\.yaml)
79
73
  .
80
- .IP "" 0
74
+ .IP
75
+ \fIReports\fR \- ($vardir/reports/node\.domain)
81
76
  .
82
77
  .IP
83
- This will unexport exported resources of a host, so that consumers of these resources can remove the exported resources and we will safely remove the node from our infrastructure\.
78
+ \fIStored configs\fR \- (in database) The clean action can either remove all data from a host in your storeconfigs database, or, with the \fI\-\-unexport\fR option, turn every exported resource supporting ensure to absent so that any other host that collected those resources can remove them\. Without unexporting, a removed node\'s exported resources become unmanaged by Puppet, and may linger as cruft unless you are purging that resource type\.
84
79
  .
85
80
  .IP
86
- \fBOPTIONS\fR \fI\-\-[no\-]unexport\fR \- Unexport exported resources
81
+ \fBOPTIONS\fR \fI\-\-[no\-]unexport\fR \- Whether to remove this node\'s exported resources from other nodes
87
82
  .
88
- .IP "\(bu" 4
89
- \fBdestroy\fR \- Invalid for this subcommand\.: \fBSYNOPSIS\fR
83
+ .TP
84
+ \fBdestroy\fR \- Invalid for this subcommand\.
85
+ \fBSYNOPSIS\fR
90
86
  .
91
87
  .IP
92
88
  puppet node destroy [\-\-terminus TERMINUS] [\-\-extra HASH] \fIkey\fR
@@ -97,8 +93,9 @@ puppet node destroy [\-\-terminus TERMINUS] [\-\-extra HASH] \fIkey\fR
97
93
  .IP
98
94
  Invalid for this subcommand\.
99
95
  .
100
- .IP "\(bu" 4
101
- \fBfind\fR \- Retrieve a node object\.: \fBSYNOPSIS\fR
96
+ .TP
97
+ \fBfind\fR \- Retrieve a node object\.
98
+ \fBSYNOPSIS\fR
102
99
  .
103
100
  .IP
104
101
  puppet node find [\-\-terminus TERMINUS] [\-\-extra HASH] \fIhost\fR
@@ -118,8 +115,9 @@ A hash containing the node\'s \fBclasses\fR, \fBenvironment\fR, \fBexpiration\fR
118
115
  .IP
119
116
  RENDERING ISSUES: Rendering as string and json are currently broken; node objects can only be rendered as yaml\.
120
117
  .
121
- .IP "\(bu" 4
122
- \fBinfo\fR \- Print the default terminus class for this face\.: \fBSYNOPSIS\fR
118
+ .TP
119
+ \fBinfo\fR \- Print the default terminus class for this face\.
120
+ \fBSYNOPSIS\fR
123
121
  .
124
122
  .IP
125
123
  puppet node info [\-\-terminus TERMINUS] [\-\-extra HASH]
@@ -128,10 +126,11 @@ puppet node info [\-\-terminus TERMINUS] [\-\-extra HASH]
128
126
  \fBDESCRIPTION\fR
129
127
  .
130
128
  .IP
131
- Prints the default terminus class for this subcommand\. Note that different run modes may have different default termini; when in doubt, specify the run mode with the \'\-\-mode\' option\.
129
+ Prints the default terminus class for this subcommand\. Note that different run modes may have different default termini; when in doubt, specify the run mode with the \'\-\-run_mode\' option\.
132
130
  .
133
- .IP "\(bu" 4
134
- \fBsave\fR \- Invalid for this subcommand\.: \fBSYNOPSIS\fR
131
+ .TP
132
+ \fBsave\fR \- Invalid for this subcommand\.
133
+ \fBSYNOPSIS\fR
135
134
  .
136
135
  .IP
137
136
  puppet node save [\-\-terminus TERMINUS] [\-\-extra HASH] \fIkey\fR
@@ -142,8 +141,9 @@ puppet node save [\-\-terminus TERMINUS] [\-\-extra HASH] \fIkey\fR
142
141
  .IP
143
142
  Invalid for this subcommand\.
144
143
  .
145
- .IP "\(bu" 4
146
- \fBsearch\fR \- Invalid for this subcommand\.: \fBSYNOPSIS\fR
144
+ .TP
145
+ \fBsearch\fR \- Invalid for this subcommand\.
146
+ \fBSYNOPSIS\fR
147
147
  .
148
148
  .IP
149
149
  puppet node search [\-\-terminus TERMINUS] [\-\-extra HASH] \fIquery\fR
@@ -154,8 +154,6 @@ puppet node search [\-\-terminus TERMINUS] [\-\-extra HASH] \fIquery\fR
154
154
  .IP
155
155
  Invalid for this subcommand\.
156
156
  .
157
- .IP "" 0
158
- .
159
157
  .SH "EXAMPLES"
160
158
  \fBfind\fR
161
159
  .
@@ -169,7 +167,7 @@ $ puppet node find somenode\.puppetlabs\.lan \-\-terminus plain \-\-render\-as y
169
167
  Retrieve a node using the puppet master\'s configured ENC:
170
168
  .
171
169
  .P
172
- $ puppet node find somenode\.puppetlabs\.lan \-\-terminus exec \-\-mode master \-\-render\-as yaml
170
+ $ puppet node find somenode\.puppetlabs\.lan \-\-terminus exec \-\-run_mode master \-\-render\-as yaml
173
171
  .
174
172
  .P
175
173
  Retrieve the same node from the puppet master:
@@ -202,6 +200,9 @@ This subcommand is an indirector face, which exposes \fBfind\fR, \fBsearch\fR, \
202
200
  \fBstore_configs\fR
203
201
  .
204
202
  .IP "\(bu" 4
203
+ \fBwrite_only_yaml\fR
204
+ .
205
+ .IP "\(bu" 4
205
206
  \fByaml\fR
206
207
  .
207
208
  .IP "" 0