[chef] Re: Re: how scrub client info out of recipes and cookbooks but also preserve commit history?

[Bryan Berry < >]

that was what I was thinking, tks

On Sat, Oct 8, 2011 at 5:56 PM, Seth Falcon < "> > wrote:

Hi Bryan,

On Sun, Oct 2, 2011 at 7:31 AM, Bryan Berry < "> > wrote:
> perhaps this is a dumb question, but is there is a straightforward way to
> scrub my recipes and cookbooks of references to a particular customer and at
> the same time maintain commit history? For example, say I have 1 recipe
> popular_framework that has references to a customer's internal
> infrastructure. Over time I will make changes to that recipe. How can I
> preserve the commit history as I merge those changes into my public github
> recipe but filter out anything specific to the customer?

You might find this page that describes how to remove history from a
git repo to be of use:
http://help.github.com/remove-sensitive-data/

The short answer is that, while possible with a few commands,
scrubbing git history is not something you want to make a regular
practice of.  So once you've cleaned your repos, it would make sense
to segregate sensitive or customer specific data in files not stored
in git.  And I think some of the other responses have suggested some
strategies along those lines in terms of data bags, for example

+ seth


--
Seth Falcon | Development Lead | Opscode | @sfalcon