On 1/07/2009, at 4:28 PM, Adam Jacob wrote:
On Wed, Jul 1, 2009 at 4:23 PM, Ian Ragsdaleian.firstname.lastname@example.org
Ok, it sounds like this would be useful to at least a few people,
even to the chef-deploy project, as it might allow them to simplify
code. Since I probably need it myself, I’m probably gonna end up
soon. Before I do, I have two questions for the opscode guys.
- Would you consider this for inclusion in Chef? I’d be happy to
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
Someone filed one when this thread started up:
“Create SCM resource and providers for git & svn”
- If the answer to #1 is yes, would you prefer this be written
grit gem, or would you prefer to have it call git on the command
can see good arguments for both, so if you guys would want to
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
The magic sauce definitely would be using gem_package internally to
get Grit if you don’t have it
You’ll wind up building:
- The repo resource, which all the other resources will inherit from
- Helper resources for the various providers, a-la gem_package, etc.
- Providers for each VCS you want to support.
We’ll be happy to help with any details of how to implement this.
Adam Jacob, CTO
T: (206) 508-4759 E: email@example.com
AJ Christensen, Software Engineer