Hi to everybody,
I'm really sorry for this late answer.
I solved the problem using Gitolite for the users code and the puppet
variable config_version to run a script for automatically updating the
environments.
I needed to do this because this is a temporary multiusers enviroment for a
tutorial on a storage system.
Thank you very much for your suggestions and help.
Cheers.
Luca
Il giorno mercoledì 13 agosto 2014 14:52:36 UTC+2, Jason Antman ha scritto:
>
> Yeah. You don't need to give them access to the master, you need something
> (I use a git hook on the git server) that deploys new pushes to the master.
>
>
> On Tue, Aug 5, 2014 at 12:15 PM, Christopher Wood <[email protected]
> <javascript:>> wrote:
>
>> Off the top of my head, have them commit/push to the same git repository
>> where that repository is checked out by the puppetmaster. You can give them
>> each a VM to test their own stuff, where they'll also find out how their
>> manifests interact with the whole picture. Keeping them in their own little
>> silos will hurt you in the long run, and also potentially much sooner than
>> that if two of them find they need to combine incompatible pieces.
>>
>> On Tue, Aug 05, 2014 at 09:00:50AM -0700, Luca Mazzaferro wrote:
>> > Dear User community,
>> > I would know if anyone has experience of using puppet
>> > with multiple developers.
>> > I try to explain better.
>> > I have ONE master and some nodes attached.
>> > We have more than 3 users which want to develop their module and
>> deploy
>> > them on different machines.
>> > I know that we can define different environments and in principle
>> > give one for each developer.
>> > But in this case I need to give the access to the master to each one
>> > and I wouldn't.
>> > In principle I would that the users develop their code on their pc,
>> then
>> > commit
>> > it via git ( for example ) and when they run puppet agent on their
>> > machines
>> > the master catch the new code and apply it.
>> > I found the config_version variable inside the environment.conf
>> should
>> > work running a git clone inside the environments
>> > before the execution on the clients.
>> > Is there another way, simpler?
>> > Anyone has any experience of it?
>> > Thank you.
>> > Regards.
>> > Luca
>> >
>> > --
>> > 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 [1][email protected] <javascript:>.
>> > To view this discussion on the web visit
>> > [2]
>> https://groups.google.com/d/msgid/puppet-users/e87c69cd-f182-463c-9c53-7225c9adfce5%40googlegroups.com
>> .
>> > For more options, visit [3]https://groups.google.com/d/optout.
>> >
>> > References
>> >
>> > Visible links
>> > 1. mailto:[email protected] <javascript:>
>> > 2.
>> https://groups.google.com/d/msgid/puppet-users/e87c69cd-f182-463c-9c53-7225c9adfce5%40googlegroups.com?utm_medium=email&utm_source=footer
>> > 3. https://groups.google.com/d/optout
>>
>> --
>> 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 [email protected] <javascript:>.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/puppet-users/20140805161502.GA9324%40iniquitous.heresiarch.ca
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
--
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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/eff6846c-d576-4ed3-9272-bd0fcef11e13%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
