Date
1 - 2 of 2
Application Releases and Rollback Feature Narrative
Troy Topnik
This narrative proposes adding Heroku-style "releases" for applications:
https://docs.google.com/document/d/1sIViZyeCri2URHAt57YW4n482cBav3b5dOgP6D_vr4A/ The feature allows developers to see a list of previous deployments of their applications (code revisions stored as a droplet, plus settings related to a particular push), and to roll back applications to a previous release. The basic functionality can already be accomplished in CF using client plugins, client-side tools, and/or manual workflows. This proposal is for a more automatic, server-side feature which could be enabled by an operator or manager. The narrative doesn't (yet) take into account some of the new Droplet APIs in v3. Suggestions on how this feature could utilize these new APIs would be very welcome. If there is overlap with other work in progress, please make a note of it here or in a comment in the doc. Thanks! TT |
|
Dieu Cao <dcao@...>
Hi Troy,
toggle quoted message
Show quoted text
Appreciate your time putting this proposal together. I believe many of these are addressed in the already in progress v3 cc api work by the CAPI team. I highly recommend attending the talk by Utako and Dan at CF Summit [1] which will review this work. There's also a CAPI project office hour at CF Summit as well [2] where you can speak with CAPI team members to discuss this further. -Dieu Runtime PMC Lead [1] http://sched.co/6ZkB [2] http://sched.co/71al On Fri, May 6, 2016 at 12:00 PM, Troy Topnik <troy.topnik(a)hpe.com> wrote:
This narrative proposes adding Heroku-style "releases" for applications: |
|