Turns out there was a very simple solution to this: Create a new modules
for the files, and deploy via r10k as part of the default environment.
Puppet Master manage thyself...
Simon.
On Friday, 1 November 2013 11:51:31 UTC, Simon Young wrote:
>
> Hi all,
>
> Apologies if this has been dealt with before, but I haven't managed to
> find an answer yet.
>
> I have a working "dynamic environments" setup:
>
> * A gitolite repository (on a dedicated host) with multiple branches - one
> for each environment.
> * I use r10k ro deploy the environments on the master to
> $confdir/environments/$::environment.
>
> This all works *really* well, but I would also like to get the rest of the
> puppet configuration under version control (i.e. puppet.conf, hiera.yaml
> etc.). It's no problem to put the files in a repo, but I'm stuck on finding
> a way to deploy them.
>
> I tried using puppetlabs/vcsrepo, but it refuses to deploy files to a
> directory that isn't a repository.
>
> So I tried blowing away $confdir, then cloning it from the repo, then
> running r10k to populate the environments subdirectory. This looked ok, but
> puppet agent runs died horribly, reporting internal server errors ("Web
> application could not be started"). I guess this may be a file permissions
> issue, but it definitely made me think I'm going about this the wrong way.
>
> Has anyone else with a similar setup managed to solve this problem? Is it
> a simple matter of moving the confdir somewhere else, or is allowing puppet
> to manage its own config simply a Bad Idea?
>
> Any pointers would be greatly appreciated!
>
> Thanks,
>
> Simon.
>
--
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/7b1f202b-98a7-470c-8538-94d31c1d9585%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
