On 9 February 2015 at 20:12, Brett Swift <[email protected]> wrote: > I'm wondering if anyone has this unique use case. > > We're going to experiment by giving our ops team their own hieradata > repository, and keep our internal repository separate.
We have a similar requirement whereby our infrastructure team (handling core FW, networking and OS-level resources) and project teams (largely deploying application-layer RPMs, but perhaps also opening up additional host-level firewall ports) need access to 2 different Git repositories so the baddies (app dev) can't stomp over the goodies' (infrastructure) hard work :-) We've ended up rolling our own synchronisation script; a common Git user has read-only access to both repositories and clones/pulls them to a staging area. It then composes them into a single YAML backend hierarchy, unlike your example where you have a 1-1 mapping between sources and backends. Regards, Matt. -- 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/CAKUTv3JJm8txYbr%3DVRM2Pv64-Cq1dSKjjFFfqS%2BJNtOxfqAbAg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
