We have a developer that has to make 3 Puppet modules for an environment. I want him to be able to write his 3 modules.

We currently write our own modules and he is the first person from another department that has to write modules. We use root-access to write/edit our modules, but we do not want to give him root access.

What is the best way to grant him rights to make/edit his 3 modules? We use the Puppet 3.2.4 and Red Hat Linux 6.4.

  • Do your developers make changes to code using root access too? – Tom O'Connor Sep 2 '13 at 15:15

Commit your modules and puppet scripts to a shared Git repository.

Your developers and this new dev can then fork the repository, and make changes, then you can merge the changes back in.

Using root access to edit files without versioning or change control is a recipe for disaster.


docs.puppetlabs.com/puppet/latest/reference/modules_fundamentals.html is a good place to start.

Publishing Modules on the Puppet Forge — Documentation — Puppet Labs :

puppet generate username-module
$EDITOR Modulefile
puppet module build <MODULE DIRECTORY>

Installing Modules — Documentation — Puppet Labs :

puppet module install --module_repository http://dev-forge.example.com username-module
puppet module upgrade --module_repository http://dev-forge.example.com username-module
  • 1
    This is surely good general advice, but how does it answer the question? – Michael Hampton Sep 2 '13 at 21:48
  • Create, Test, Share/Publish (Git Push, Pull), Install, Upgrade. – Wes Turner Sep 3 '13 at 9:19

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.