Staging and Runtime Hooks Feature Narrative


Troy Topnik
 

This feature allows developers more control of the staging and deployment of their application code, without them having to fork existing buildpacks or create their own.

https://docs.google.com/document/d/1PnTtTLwXOTG7f70ilWGlbTbi1LAXZu9zYnrUVvjr31I/edit

Hooks give developers the ability to optionally:
* run scripts in the staging container before and/or after the bin/compile scripts executed by the buildpack, and
* run scripts in each app container before the app starts (via .profile as per the Heroku buildpack API)

A similar feature has been available and used extensively in Stackato for a few years, and we'd like to contribute this functionality back to Cloud Foundry.

A proof-of-concept of this feature has already been submitted as a pull request, and the Feature Narrative addresses many of the questions raised in the PR discussion:

https://github.com/cloudfoundry-incubator/buildpack_app_lifecycle/pull/13

Please weigh in with comments in the document itself or in this thread.

Thanks,

TT

Join cf-dev@lists.cloudfoundry.org to automatically receive all group messages.