- From: Sol Kindle <
>
- To:
- Subject: [chef-dev] Extending Chef Deploy for Object Storage Services
- Date: Wed, 8 May 2013 17:22:34 -0700
Ohai devs!
I'm finally had a chance to play around with deploy resource and application cookbooks. While the deploy resource is pretty complicated, it works great and has an amazing amount of flexibility.
I have a requirement to deploy application code from tarballs living in an object storage service (e.g. S3) -- this so we don't depend on github being available during an autoscaling event. I have to support all kinds of app stacks, including rails, tomcat and php.
I just wanted to get some expert eyes on this idea to see if there is any value in it and if this approach is the right direction.
Here are some more details about what I am thinking...
Questions:
- Does it make sense to extend the deploy and scm resources to support an ObjectStorage SCM resource and providers?
- Does the way of matching archive filenames and the naming conventions make sense?
- Other thoughts?
Thanks!
@kindsol (aka caryp)
- [chef-dev] Extending Chef Deploy for Object Storage Services, Sol Kindle, 05/08/2013
Archive powered by MHonArc 2.6.16.