[chef] Re: Re: Re: Re: source repositories as resources?

[Arjuna Christensen <aj@opscode.com>]

On 1/07/2009, at 4:28 PM, Adam Jacob wrote:

On Wed, Jul 1, 2009 at 4:23 PM, Ian Ragsdale<ian.ragsdale@gmail.com> wrote:

Ok, it sounds like this would be useful to at least a few people, perhaps

even to the chef-deploy project, as it might allow them to simplify their

code.  Since I probably need it myself, I'm probably gonna end up writing it

soon.  Before I do, I have two questions for the opscode guys.

1) Would you consider this for inclusion in Chef?  I'd be happy to donate it

and would love to not have to maintain and install it separately.

Absolutely.  File a ticket for the new feature, and then publish it up
to Github.

Someone filed one when this thread started up:

http://tickets.opscode.com/browse/CHEF-419

"Create SCM resource and providers for git & svn"

2) If the answer to #1 is yes, would you prefer this be written using the

grit gem, or would you prefer to have it call git on the command line?  I

can see good arguments for both, so if you guys would want to include it

then I'd go with whatever you prefer.

I think it's fine to use the Grit gem - you can probably also include
some logic in the Git provider to auto-install the gem if you don't
have it already on first use of the provider.

Maybe a generic Git provider that abstracts both Grit and the Git binaries away, then you can 'provider Chef::Provider::Git::Grit' in your resources.

The magic sauce definitely would be using gem_package internally to get Grit if you don't have it :)

You'll wind up building:

1) The repo resource, which all the other resources will inherit from
2) Helper resources for the various providers, a-la gem_package, etc.
3) Providers for each VCS you want to support.

We'll be happy to help with any details of how to implement this.

Best,
Adam

--
Opscode, Inc.
Adam Jacob, CTO
T: (206) 508-4759 E: adam@opscode.com

-- 
AJ Christensen, Software Engineer

Opscode, Inc.
E: aj@opscode.com