Thanks for the reply! I agree that the 'ark' resource shares some similar features. There are also some potential features in ark that would be nice to "borrow" for this proposed SCM provider. Whereas, the main purpose for ark is to do the "fetch-unpack-configure-build-install dance" for building/installing binaries, the purpose of this ObjectSCM provider is to fetch web application code in a way that we can leverage the all the migration, callback and rollback functionality offered by the existing Deploy Resource[1]. I have updated the overview and implementation sections in an attempt to be more clear about that. I have also renamed the proposed provider to "Chef::Provider::ScmObject". Please see: Cheers! - CaryP On May 8, 2013, at 6:13 PM, Ranjib Dey wrote:
|
Archive powered by MHonArc 2.6.16.