- Installation
- Basic usage
- Experimental features
- Module compatibility
- Contributing
- Contact Information
The Puppet Development Kit (PDK) includes key Puppet code development and testing tools for Linux, Windows, and OS X workstations, so you can install one package with the tools you need to create and validate new modules.
PDK includes testing tools, a complete module skeleton, and command line tools to help you create, validate, and run tests on Puppet modules. PDK also includes all dependencies needed for its use.
PDK includes the following tools:
| Tool | Description | Owned by Puppet |
|---|---|---|
| facterdb | A gem that contains facts for Operating Systems. | N |
| metadata-json-lint | Validates and lints metadata.json files in modules against Puppet module metadata style guidelines. |
N |
| pdk | Tool to generate and test modules and module content, such as classes, from the command line. | Y |
| puppet-debugger | Provides a REPL based debugger console. | N |
| puppet-lint | Checks your Puppet code against the recommendations in the Puppet language style guide. | Y |
| puppet-syntax | Checks for correct syntax in Puppet manifests, templates, and Hiera YAML. | N |
| puppetlabs_spec_helper | Provides classes, methods, and Rake tasks to help with spec testing Puppet code. | Y |
| rspec-puppet | Tests the behavior of Puppet when it compiles your manifests into a catalog of Puppet resources. | Y |
| rspec-puppet-facts | Adds support for running rspec-puppet tests against the facts for your supported operating systems. |
N |
Download and install the newest package matching your platform from the download page. If you are using Windows, remember to close any open PowerShell windows.
For complete installation information, see the PDK documentation.
PDK can generate modules and classes, validate module metadata, style, and syntax, and run unit tests. This README contains very basic usage information---for complete usage information, see the PDK documentation.
Generates the basic components of a module and set up an infrastructure for testing it with PDK.
- Run the
pdk new modulecommand, specifying the name of the new module:
pdk new module my_module
This command asks a series of metadata questions and then generates the basic components of a new module.
To generate a class in your module, use the pdk new class command, specifying the name of your new class. To generate the main class of the module, which is defined in an init.pp file, give the class the same name as the module.
- From the command line, in your module's directory, run:
pdk new class class_name
PDK creates the new class manifest and a test file (as class_name_spec.rb) in your module's /spec/classes directory.
To generate a defined type in your module, use the pdk new defined_type command, specifying the name of your new defined type.
- From the command line, in your module's directory, run:
pdk new defined_type defined_type_name
PDK creates the new defined_type manifest and a test file (as defined_type_name_spec.rb) in your module's /spec/defines directory.
To generate a task in your module, use the pdk new task command, specifying the name of your new task.
- From the command line, in your module's directory, run:
pdk new task task_name
PDK creates the new task file and metadata.
PDK can validate the well-formedness of the module and style and syntax of its files.
- In the module's directory, run:
pdk validate
This command validates the metadata, Puppet code syntax and style, and Ruby syntax and style for the entire module.
PDK's default template sets up rspec for Ruby-level unit testing, and rspec-puppet for catalog-level unit testing.
In the module's directory, run unit tests with:
pdk test unit
This command runs all available unit tests.
The pdk console command executes a session of the puppet debugger when inside a module and allows for exploration of puppet code. See the official puppet debugger site for more info and the official docs site here.
To use, execute pdk console from inside your module directory. You can also supply the --puppet-version or --pe-version or --puppet-dev to swap out the puppet version when using the console.
Example (from within a module):
pdk console --puppet-version=5pdk console --pe-version=2018.1
The pdk console command will also pass through any puppet debugger arguments you wish to use.
Example:
pdk console --no-facterdbpdk console --play https://gist.github.com/logicminds/4f6bcfd723c92aad1f01f6a800319fa4pdk console -e "md5('sdfasdfasdf')" --run-once --quiet
Use pdk console -h for a further explanation of pass through arguments.
If you receive the following error you do not have the puppet-debugger gem installed.
pdk console -h
Error: Unknown Puppet subcommand 'debugger'
See 'puppet help' for help on available puppet subcommands
To fix this you will need to add the following entry to your .sync.yml file and run pdk update:
Gemfile:
required:
":development":
- gem: puppet-debugger
version: "~> 0.14"
NOTE: The puppet-debugger gem has been added to the puppet-module-* gems, so once you get the gem update you no longer need the .sync.yml entry.
This command executes arbitrary commands in a bundler context within the module you're currently working on. Arguments to this command are passed straight through to bundler. This command is experimental and can lead to errors that can't be resolved by PDK itself.
PDK Version Compatibility: Modules created with PDK validate against and run on all Puppet and Ruby version combinations currently under maintenance (see https://docs.puppet.com/puppet/latest/about_agent.html and https://puppet.com/misc/puppet-enterprise-lifecycle)
PDK encourages community contributions. See the CONTRIBUTING.md file for development notes.
To contact us with questions: pdk-maintainers@puppet.com