Hi everyone,

It is my great pleasure to release the first Tech Preview of the new Puppet
Development Kit <https://github.com/puppetlabs/pdk> (PDK) to the Puppet
community. The open-source PDK facilitates an easy, unified development
workflow for Puppet modules, and should appeal both to newcomers and
experienced developers.

With the PDK you can:

   -

   Quickly get started with module development best practices and tools to
   develop, test and publish high-quality Puppet modules with confidence
   -

   Shift quality to the left by catching issues earlier and faster, before
   Puppet code is applied to live infrastructure
   -

   Unit test modules from their workstation to ensure that Puppet code is
   creating and managing resources as intended


You can learn more about how to install and use the PDK by reviewing the
README (https://github.com/puppetlabs/pdk) or a draft of the official
Getting Started guide (
https://gist.github.com/jbondpdx/8a315b47585f3ee34729d0c99ff04192).

OS native packages are available at https://goo.gl/fkAEwT. The OS native
packages constitute a complete, "batteries-included" development
environment including Ruby and all other dependencies necessary for using
the PDK.

In addition, the core 'pdk' gem is available on Rubygems (
https://rubygems.org/gems/pdk).

Note that we consider this a pre-release/tech preview. This iteration of
the PDK is feature complete and we want to get your feedback now as we work
towards a 1.0 release.

Please report any issues you find as a ticket on the PDK (
https://github.com/puppetlabs/pdk/issues/) project in GitHub.

Known Issues

   -

   Linux and Mac OS users need to manually add /opt/puppetlabs/bin to their
   PATH
   -

   If you have an active RVM-installed Ruby, a packaged installation of PDK
   may not work correctly. As a temporary workaround, you can run PDK with the
   GEM_HOME and GEM_PATH environment variables unset. (For example: “env -u
   GEM_HOME -u GEM_PATH pdk <subcommand>”) This issue will be fixed in a
   future release.
   -

   Windows packages require PowerShell 5+ and a script “ExecutionPolicy” of
   at least “RemoteSigned” (Future releases will work all the way up to
   “AllSigned”.)


Lindsey

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CAPyei8X7%3Da7Hp-hMSS8ogmbHJ95hj9C2Gxm9CSSzQrdps_QwJA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to