43. Answer these
questions
• What technology does your module
manage?
• What does it intend to do?
• How does it do it? (impact on the
system)
• How should one use it?
46. Semantic Versioning
• Based on Major.Minor.Patch scheme
• X.0.0 Major version for breaking change
• 0.X.0 Minor version for new non-breaking
functionality
• 0.0.X Patch version for backwards compatible
bug fixes
61. Data Lookup Order
•
Use explicit class declaration
values
•
•
•
Query Data Binding
Use the default value from class.
Fail compilation with an error if no
value can be found.
79. Thank You!
Feel free to email or tweet anytime RE: Forge!
ryan@puppetlabs.com - @ryanycoleman
forge.puppetlabs.com
#PuppetCamp
Editor's Notes
Ryan was a RedHat sysadmin for Penn State before joining Puppet Labs
as a professional services engineer. Now is product owner for the Forge.
The Puppet Forge is a community driven web service for contributing and finding Puppet modules.
The following are examples of what you will find on the Forge.
Many Puppet modules offer users way too many interaction points or one massive entry point that is too difficult to comprehend. The end result isn’t user friendly and doesn’t help with maintenance either.
The answer, use Hiera!
Seriously, these docs rock. Read them. http://docs.puppetlabs.com/hiera/1/index.html
But really, just get yourself onto Puppet 3 and take advantage of automatic Hiera!
This slide could be more visual vs text-based
There’s already an alternative out there, for consulting foreman as your data backend
Hiera backends are pluggable too. Here are two examples.
If you want to add your influence to our products, join the Puppet Labs Test Pilots program!
https://puppetlabs.com/community/puppet-test-pilots-program/