git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: offtopic: ppg design decisions - encapsulation

From
John Keeping <john@keeping.me.uk>
Date
May 6, 2013, 15:53 UTC
Message-ID
<20130506155353.GF25912@serenity.lan>
In-Reply-To
<CACPiFCL+cd1vmqj6JEj84L5rDvHGxDgo+zGw5__ard6-sumipA@mail.gmail.com>
On Mon, May 06, 2013 at 11:34:28AM -0400, Martin Langhoff wrote:
Show 15 quoted lines
> [ Unashamedly offtopic... asking here because I like git design and
> coding style, and ppg is drawing plenty of inspiration from the old
> git shell scripts. Please kindly flame me privately... ]
> 
> ppg is a wrapper around git to maintain and distribute Puppet configs,
> adding a few niceties.
> 
> Now, ppg will actuall manage two git repositories -- one for the
> puppet configs, the second one for ferrying back the puppet run
> results to the originating repo (were they get loaded in a puppet
> dashboard server for cute webbased reporting). The puppet config repo
> is a normally-behaved git repo. The "reports" repo is a bit of a hack
> -- never used directly by the user, it will follow a store-and-forward
> scheme, where I should trim old history or just use something other
> than git.

I'm not sure I fully understand what the reports are, but it sounds like they are closely related to original configuration commits. If that is the case, have you considered using Git notes instead of a separate repository?

Previous: Martin LanghoffNext: Martin Langhoff
Message 2 of 3 in “offtopic: ppg design decisions - encapsulation”
  1. Martin LanghoffMay 6, 2013
  2. John KeepingMay 6, 2013
  3. Martin LanghoffMay 7, 2013

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.