pdk 0.0.1 → 0.1.0

Sign up to get free protection for your applications and to get access to all the features.
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA1:
3
- metadata.gz: 4b8385f5fba8083edb1654843d8880f2f3dccf61
4
- data.tar.gz: 33b6c7c4b76e87d71ff0cb7e9f2abdc20abebc9f
3
+ metadata.gz: 6475b9cccfedb258b4accc3ce84b407f4f530480
4
+ data.tar.gz: 29aeb6521f3b3ee7bd41e2ade024e9a75a79692d
5
5
  SHA512:
6
- metadata.gz: fdcca54d273721062f9d0cc52b1a7229e9dcf9f4b0ff6258e688d491ba91be2b18b4a8f1acbf5cc2f726f20b4e321fe53af794e10d3f997db4f6770005fe1bd7
7
- data.tar.gz: 75aef45bbb2d901e09c1076be2c2153c3d5d792d105ce3d7a5dbd3380daa86fcc5a275e7273fe752c60e746491a66cb4057178462131296f62130465eecc312e
6
+ metadata.gz: bead00ff5d38bdf51ea0035b60a1d9a0f4ef111c982e14295dc4dbbe47a2bec0fd9d1d160c3267c98c73fde9ccd9beec9d3e95aae340b12ae9232649c3b27502
7
+ data.tar.gz: ac72b4f88da4a89fdda9377e430b040f0cb3dbba59aa4d7f6cfab3879abd3005ac00bdff70ee2b4bc7ea1e307da1b94eccaa62387e8b76fab79487cd563177ba
data/LICENSE ADDED
@@ -0,0 +1,201 @@
1
+ Apache License
2
+ Version 2.0, January 2004
3
+ http://www.apache.org/licenses/
4
+
5
+ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
6
+
7
+ 1. Definitions.
8
+
9
+ "License" shall mean the terms and conditions for use, reproduction,
10
+ and distribution as defined by Sections 1 through 9 of this document.
11
+
12
+ "Licensor" shall mean the copyright owner or entity authorized by
13
+ the copyright owner that is granting the License.
14
+
15
+ "Legal Entity" shall mean the union of the acting entity and all
16
+ other entities that control, are controlled by, or are under common
17
+ control with that entity. For the purposes of this definition,
18
+ "control" means (i) the power, direct or indirect, to cause the
19
+ direction or management of such entity, whether by contract or
20
+ otherwise, or (ii) ownership of fifty percent (50%) or more of the
21
+ outstanding shares, or (iii) beneficial ownership of such entity.
22
+
23
+ "You" (or "Your") shall mean an individual or Legal Entity
24
+ exercising permissions granted by this License.
25
+
26
+ "Source" form shall mean the preferred form for making modifications,
27
+ including but not limited to software source code, documentation
28
+ source, and configuration files.
29
+
30
+ "Object" form shall mean any form resulting from mechanical
31
+ transformation or translation of a Source form, including but
32
+ not limited to compiled object code, generated documentation,
33
+ and conversions to other media types.
34
+
35
+ "Work" shall mean the work of authorship, whether in Source or
36
+ Object form, made available under the License, as indicated by a
37
+ copyright notice that is included in or attached to the work
38
+ (an example is provided in the Appendix below).
39
+
40
+ "Derivative Works" shall mean any work, whether in Source or Object
41
+ form, that is based on (or derived from) the Work and for which the
42
+ editorial revisions, annotations, elaborations, or other modifications
43
+ represent, as a whole, an original work of authorship. For the purposes
44
+ of this License, Derivative Works shall not include works that remain
45
+ separable from, or merely link (or bind by name) to the interfaces of,
46
+ the Work and Derivative Works thereof.
47
+
48
+ "Contribution" shall mean any work of authorship, including
49
+ the original version of the Work and any modifications or additions
50
+ to that Work or Derivative Works thereof, that is intentionally
51
+ submitted to Licensor for inclusion in the Work by the copyright owner
52
+ or by an individual or Legal Entity authorized to submit on behalf of
53
+ the copyright owner. For the purposes of this definition, "submitted"
54
+ means any form of electronic, verbal, or written communication sent
55
+ to the Licensor or its representatives, including but not limited to
56
+ communication on electronic mailing lists, source code control systems,
57
+ and issue tracking systems that are managed by, or on behalf of, the
58
+ Licensor for the purpose of discussing and improving the Work, but
59
+ excluding communication that is conspicuously marked or otherwise
60
+ designated in writing by the copyright owner as "Not a Contribution."
61
+
62
+ "Contributor" shall mean Licensor and any individual or Legal Entity
63
+ on behalf of whom a Contribution has been received by Licensor and
64
+ subsequently incorporated within the Work.
65
+
66
+ 2. Grant of Copyright License. Subject to the terms and conditions of
67
+ this License, each Contributor hereby grants to You a perpetual,
68
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
69
+ copyright license to reproduce, prepare Derivative Works of,
70
+ publicly display, publicly perform, sublicense, and distribute the
71
+ Work and such Derivative Works in Source or Object form.
72
+
73
+ 3. Grant of Patent License. Subject to the terms and conditions of
74
+ this License, each Contributor hereby grants to You a perpetual,
75
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
76
+ (except as stated in this section) patent license to make, have made,
77
+ use, offer to sell, sell, import, and otherwise transfer the Work,
78
+ where such license applies only to those patent claims licensable
79
+ by such Contributor that are necessarily infringed by their
80
+ Contribution(s) alone or by combination of their Contribution(s)
81
+ with the Work to which such Contribution(s) was submitted. If You
82
+ institute patent litigation against any entity (including a
83
+ cross-claim or counterclaim in a lawsuit) alleging that the Work
84
+ or a Contribution incorporated within the Work constitutes direct
85
+ or contributory patent infringement, then any patent licenses
86
+ granted to You under this License for that Work shall terminate
87
+ as of the date such litigation is filed.
88
+
89
+ 4. Redistribution. You may reproduce and distribute copies of the
90
+ Work or Derivative Works thereof in any medium, with or without
91
+ modifications, and in Source or Object form, provided that You
92
+ meet the following conditions:
93
+
94
+ (a) You must give any other recipients of the Work or
95
+ Derivative Works a copy of this License; and
96
+
97
+ (b) You must cause any modified files to carry prominent notices
98
+ stating that You changed the files; and
99
+
100
+ (c) You must retain, in the Source form of any Derivative Works
101
+ that You distribute, all copyright, patent, trademark, and
102
+ attribution notices from the Source form of the Work,
103
+ excluding those notices that do not pertain to any part of
104
+ the Derivative Works; and
105
+
106
+ (d) If the Work includes a "NOTICE" text file as part of its
107
+ distribution, then any Derivative Works that You distribute must
108
+ include a readable copy of the attribution notices contained
109
+ within such NOTICE file, excluding those notices that do not
110
+ pertain to any part of the Derivative Works, in at least one
111
+ of the following places: within a NOTICE text file distributed
112
+ as part of the Derivative Works; within the Source form or
113
+ documentation, if provided along with the Derivative Works; or,
114
+ within a display generated by the Derivative Works, if and
115
+ wherever such third-party notices normally appear. The contents
116
+ of the NOTICE file are for informational purposes only and
117
+ do not modify the License. You may add Your own attribution
118
+ notices within Derivative Works that You distribute, alongside
119
+ or as an addendum to the NOTICE text from the Work, provided
120
+ that such additional attribution notices cannot be construed
121
+ as modifying the License.
122
+
123
+ You may add Your own copyright statement to Your modifications and
124
+ may provide additional or different license terms and conditions
125
+ for use, reproduction, or distribution of Your modifications, or
126
+ for any such Derivative Works as a whole, provided Your use,
127
+ reproduction, and distribution of the Work otherwise complies with
128
+ the conditions stated in this License.
129
+
130
+ 5. Submission of Contributions. Unless You explicitly state otherwise,
131
+ any Contribution intentionally submitted for inclusion in the Work
132
+ by You to the Licensor shall be under the terms and conditions of
133
+ this License, without any additional terms or conditions.
134
+ Notwithstanding the above, nothing herein shall supersede or modify
135
+ the terms of any separate license agreement you may have executed
136
+ with Licensor regarding such Contributions.
137
+
138
+ 6. Trademarks. This License does not grant permission to use the trade
139
+ names, trademarks, service marks, or product names of the Licensor,
140
+ except as required for reasonable and customary use in describing the
141
+ origin of the Work and reproducing the content of the NOTICE file.
142
+
143
+ 7. Disclaimer of Warranty. Unless required by applicable law or
144
+ agreed to in writing, Licensor provides the Work (and each
145
+ Contributor provides its Contributions) on an "AS IS" BASIS,
146
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
147
+ implied, including, without limitation, any warranties or conditions
148
+ of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
149
+ PARTICULAR PURPOSE. You are solely responsible for determining the
150
+ appropriateness of using or redistributing the Work and assume any
151
+ risks associated with Your exercise of permissions under this License.
152
+
153
+ 8. Limitation of Liability. In no event and under no legal theory,
154
+ whether in tort (including negligence), contract, or otherwise,
155
+ unless required by applicable law (such as deliberate and grossly
156
+ negligent acts) or agreed to in writing, shall any Contributor be
157
+ liable to You for damages, including any direct, indirect, special,
158
+ incidental, or consequential damages of any character arising as a
159
+ result of this License or out of the use or inability to use the
160
+ Work (including but not limited to damages for loss of goodwill,
161
+ work stoppage, computer failure or malfunction, or any and all
162
+ other commercial damages or losses), even if such Contributor
163
+ has been advised of the possibility of such damages.
164
+
165
+ 9. Accepting Warranty or Additional Liability. While redistributing
166
+ the Work or Derivative Works thereof, You may choose to offer,
167
+ and charge a fee for, acceptance of support, warranty, indemnity,
168
+ or other liability obligations and/or rights consistent with this
169
+ License. However, in accepting such obligations, You may act only
170
+ on Your own behalf and on Your sole responsibility, not on behalf
171
+ of any other Contributor, and only if You agree to indemnify,
172
+ defend, and hold each Contributor harmless for any liability
173
+ incurred by, or claims asserted against, such Contributor by reason
174
+ of your accepting any such warranty or additional liability.
175
+
176
+ END OF TERMS AND CONDITIONS
177
+
178
+ APPENDIX: How to apply the Apache License to your work.
179
+
180
+ To apply the Apache License to your work, attach the following
181
+ boilerplate notice, with the fields enclosed by brackets "{}"
182
+ replaced with your own identifying information. (Don't include
183
+ the brackets!) The text should be enclosed in the appropriate
184
+ comment syntax for the file format. We also recommend that a
185
+ file or class name and description of purpose be included on the
186
+ same "printed page" as the copyright notice for easier
187
+ identification within third-party archives.
188
+
189
+ Copyright {yyyy} {name of copyright owner}
190
+
191
+ Licensed under the Apache License, Version 2.0 (the "License");
192
+ you may not use this file except in compliance with the License.
193
+ You may obtain a copy of the License at
194
+
195
+ http://www.apache.org/licenses/LICENSE-2.0
196
+
197
+ Unless required by applicable law or agreed to in writing, software
198
+ distributed under the License is distributed on an "AS IS" BASIS,
199
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
200
+ See the License for the specific language governing permissions and
201
+ limitations under the License.
@@ -0,0 +1,270 @@
1
+ # pdk [![Travis Build Status](https://travis-ci.com/puppetlabs/pdk.svg?token=kFfyquZWxwxpgSetpypR&branch=master)](https://travis-ci.com/puppetlabs/pdk) [![Appveyor Build Status](https://ci.appveyor.com/api/projects/status/x70e2fqllbaootpd?svg=true)](https://ci.appveyor.com/project/puppetlabs/pdk)
2
+
3
+
4
+ A CLI to facilitate easy, unified development workflows for Puppet modules. pdk is a key part of the Puppet Development Kit, the shortest path to better modules.
5
+
6
+ ## Installation
7
+
8
+ 1. Until Puppet Development Kit packaging is available, install `pdk` into your Ruby installation with:
9
+
10
+ ```
11
+ $ gem install pdk
12
+ ```
13
+
14
+ ## Usage
15
+
16
+ ### Generate a new module
17
+
18
+ To get started, generate a new module from the default template.
19
+
20
+ 1. Run the `pdk new module` command, specifying the name of the new module:
21
+
22
+ ```
23
+ pdk new module my_module
24
+ ```
25
+
26
+ This generates the basic components of a new module and initializes Git for you. The `pdk new module` command sets some default values based on your environment. Check the `metadata.json` to make sure that these values are correct. The new module now contains all the infrastructure to use the other capabilities of `pdk`.
27
+
28
+ ### Add a new resource provider
29
+
30
+ If you need to manage a specific resource that is not covered by either Puppet's basic resource types or an existing module, create a new resource provider.
31
+
32
+ 1. From within an existing module, run `pdk add provider`, specifying the new provider name as well as any attributes along with their data types.
33
+
34
+ For example:
35
+
36
+ ```
37
+ pdk add provider new_provider String:content 'Enum[absent, present]:ensure'
38
+ ```
39
+
40
+ This creates all the files required to define a resource type, its provider, and the associated basic tests. In this example, the resource type has an `ensure` property with the expected values, and a `String` property named `content`. If your types use Bash special characters, such as 'Enum[absent, present]:ensure' above, you must quote to avoid issues with the shell.
41
+
42
+ ### Running validations
43
+
44
+ The default template provides tools for running static validations of your new module. Validations run quickly, but they provide only a basic check of the well-formedness of the module and syntax of its files.
45
+
46
+ ```
47
+ pdk validate
48
+ ```
49
+
50
+ This displays results in the console:
51
+
52
+ ```
53
+ Running validations on `new_module`:
54
+ * ruby syntax: OK!
55
+ * puppet syntax: OK!
56
+ [...]
57
+ ```
58
+
59
+ ### Run unit tests
60
+
61
+ The default template sets up [rspec](http://rspec.info/) for Ruby-level unit testing, and [rspec-puppet](https://github.com/rodjek/rspec-puppet/) for catalog-level unit testing.
62
+
63
+ 1. In the module's directory, run all unit tests with:
64
+
65
+ ```
66
+ pdk test unit
67
+ ```
68
+
69
+ <!-- // TODO: git hosting services (integration); code manager workflow integration; CI/CD Integration -->
70
+
71
+
72
+ ## Reference
73
+
74
+ ### `pdk new module` command
75
+
76
+ Generates a new module.
77
+
78
+ Usage:
79
+
80
+ ```
81
+ pdk new module [--template-url=git_url] [--license=spdx_identifier] [--vcs=vcs_provider] module_name [target_dir]
82
+ ```
83
+
84
+ The `pdk new module` command accepts the following arguments and options. Arguments are optional unless otherwise specified.
85
+
86
+ #### `--template-url=git_url`
87
+
88
+ Overrides the template to use for this module. If possible, please contribute your improvements back to the default template at [puppetlabs/pdk-module-template](https://github.com/puppetlabs/pdk-module-template).
89
+
90
+ #### `--license=spdx_identifier`
91
+
92
+ Specifies the license this module is written under. See https://spdx.org/licenses/ for a list of open source licenses, or use `proprietary`. Defaults to `Apache-2.0`.
93
+
94
+ #### `--vcs=vcs_provider`
95
+
96
+ Specifies the version control driver. Valid values: `git`, `none`. Default: `git`.
97
+
98
+ #### `--skip-interview`
99
+
100
+ Suppress interactive queries for initial values. All questions will use the default values.
101
+
102
+ #### `module_name`
103
+
104
+ **Required**. Specifies the name of the module being created, including the namespace. e.g.: `username-my_module`
105
+
106
+ #### `target_dir`
107
+
108
+ Specifies the directory that the new module will be created in. Defaults to creating a new directory with the given `module_name` inside the current directory.
109
+
110
+ ### `pdk new class` command
111
+
112
+ Generates a new class and skeleton test for it in the current module.
113
+
114
+ Usage:
115
+
116
+ ```
117
+ pdk new class [--template-url=git_url] <class_name> [parameter_name[:parameter_type]] [parameter_name[:parameter_type]] ...
118
+ ```
119
+
120
+ e.g.
121
+
122
+ ```
123
+ cd my_module
124
+ pdk new class my_class "ensure:Enum['absent', 'present']" version:String
125
+ ```
126
+
127
+ #### `--template-url`
128
+
129
+ Overrides the template to use when generating this class. If this is not
130
+ specified, the template used to generate the module will be used instead. If
131
+ that template is not available, the default template at
132
+ [puppetlabs/pdk-module-template](https://github.com/puppetlabs/pdk-module-template)
133
+ will be used.
134
+
135
+ #### `class_name`
136
+
137
+ The name of the class to generate. If the class name is not inside the module
138
+ namespace (e.g. module name is `apt` and the class name is `source`, then the
139
+ module name will automatically be prepended to the class name (e.g.
140
+ `apt::source`).
141
+
142
+ #### `parameter_name[:parameter_type]`
143
+
144
+ If the class should take parameters, they can be specified on the command line
145
+ to be added to the generated class. Optionally, the data type of the parameter
146
+ can be specified along with the parameter name, separated by a colon. Any
147
+ number of parameters can be provided on the command line.
148
+
149
+ ### `pdk add provider` command
150
+
151
+ Adds a new resource provider to an existing module.
152
+
153
+ Usage:
154
+
155
+ ```
156
+ pdk add provider [--template-url=git_url] provider_name [data_type:attribute_name]*
157
+ ```
158
+
159
+ The `pdk add provider` command accepts the following arguments. Arguments are optional unless specified.
160
+
161
+ #### `--template-url=git_url`
162
+
163
+ Overrides the template to use for this module. If possible please contribute your improvements back to the default template at [puppetlabs/pdk](https://github.com/puppetlabs/pdk).
164
+
165
+ #### `provider_name`
166
+
167
+ **Required**. Specifies the name of the resource provider being created.
168
+
169
+ #### `data_type:attribute_name`
170
+
171
+ Specifies a list of attributes with their expected data types, such as `'Enum[absent, present]:ensure'`. If not specified, the data type will have no attributes.
172
+
173
+ ### `pdk validate` command
174
+
175
+ Runs all static validations. Any errors are reported to the console in the format requested. The exit code is non-zero when errors occur.
176
+
177
+ Usage:
178
+
179
+ ```
180
+ pdk validate --list
181
+ ```
182
+
183
+ ```
184
+ pdk validate [--format=format[:target]] [validations] [targets*]
185
+ ```
186
+
187
+ #### `--list`
188
+
189
+ Displays a list of available validations and their descriptions. Using this option lists the tests without running them.
190
+
191
+ #### `--format=format[:target]`
192
+
193
+ Specifies the format of the output. Valid values: `junit`, `text`. Default: `text`.
194
+
195
+ Optionally, you can specify a target file for the given output format with the syntax: `--format=junit:report.xml`
196
+
197
+ Multiple `--format` options can be specified as long as they all have distinct output targets.
198
+
199
+ #### `validations`
200
+
201
+ Specifies a comma separated list of validations to run (or `all`). See the `--list` output for a list of available validations. Defaults to `all` if not supplied.
202
+
203
+ #### `targets`
204
+
205
+ Specifies a list of directories or individual files to validate. Validations which are not applicable to individual files will be skipped for those files. Defaults to validating everything.
206
+
207
+ #### Additional Examples
208
+
209
+ ```
210
+ $ pdk validate metadata
211
+ Running 'metadata' validation on `new_module`: OK!
212
+ ```
213
+
214
+ ```
215
+ $ pdk validate all lib/
216
+ Running validations on `new_module/lib`:
217
+ * ruby syntax: OK!
218
+ * puppet syntax: (no puppet manifests found)
219
+ ```
220
+
221
+ #### `pdk test unit` command
222
+
223
+ Runs unit tests. Any errors are displayed to the console and reported in the report-file, if requested. The exitcode is non-zero when errors occur.
224
+
225
+ Usage:
226
+
227
+ ```
228
+ pdk test unit [--list] [--tests=test_list] [--format=format[:target]] [runner_options]
229
+ ```
230
+
231
+ #### `--list`
232
+
233
+ Displays a list of unit tests and their descriptions. Using this option lists the tests without running them.
234
+
235
+ #### `--tests=test_list`
236
+
237
+ A comma-separated list of tests to run. Use this during development to pinpoint a single failing test. See the `--list` output for allowed values.
238
+
239
+ #### `--format=format[:target]`
240
+
241
+ Specifies the format of the output. Valid values: `junit`, `text`. Default: `text`.
242
+
243
+ Optionally, you can specify a target file for the given output format with the syntax: `--format=junit:report.xml`
244
+
245
+ Multiple `--format` options can be specified as long as they all have distinct output targets.
246
+
247
+ #### `runner_options`
248
+
249
+ <!-- this is a cop-out; alternatives are surfacing the real runner to advanced users, or completely wrapping the runner's interface -->
250
+
251
+ Specifies options to pass through to the actual test-runner. In the default template (and most commonly across modules), this is [rspec](https://relishapp.com/rspec/rspec-core/docs/command-line).
252
+
253
+ ## Contributing
254
+
255
+ To run the `pdk` tool directly from the repository, set the environment variable `PDK_USE_SYSTEM_BINARIES` to `true`. This causes it to use the system installed binaries, instead of relying on the puppet-sdk-vanagon packaging. Currently required is a ruby (2.1, or later), and git.
256
+
257
+ ```
258
+ PowerShell: $env:PDK_USE_SYSTEM_BINARIES = "true"
259
+ cmd.exe: set PDK_USE_SYSTEM_BINARIES=true
260
+ bash: export PDK_USE_SYSTEM_BINARIES=true
261
+ ```
262
+
263
+ In cases where `pdk` needs to run in a working directory outside the cloned repository, either set `BUNDLE_GEMFILE` to the pdk's Gemfile location, or install and use the [binstubs of bundler](http://bundler.io/v1.15/bundle_binstubs.html), which are small proxy binaries, that set up the environment for running the tool.
264
+
265
+ ```
266
+ # assuming ~/bin is already on your path:
267
+ bundle binstubs pdk --path ~/bin
268
+ ```
269
+
270
+ Bug reports and pull requests are welcome on GitHub at https://github.com/puppetlabs/pdk.