Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

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.

share|improve this question
Do your developers make changes to code using root access too? – Tom O'Connor Sep 2 '13 at 15:15
up vote 11 down vote accepted

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.

share|improve this answer 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 username-module
puppet module upgrade --module_repository username-module
share|improve this answer
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 posting your answer, you agree to the privacy policy and terms of service.

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