Deploy application: Override manifest fields about stratos HOT 3 CLOSED

We have created an issue in Pivotal Tracker to manage this. Unfortunately, the Pivotal Tracker project is private so you may be unable to view the contents of the story.

The labels on this github issue will be updated when the story is started.

from stratos.

Approaches
[update] We'll go with the first one

• Allow users to provide values in UX that can be used as extra params in cf push command
  • How do we redeploy with the same settings? Should they be stored in the 'STRATOS_PROJECT' env var? What if this is sensitive data?
  • Few steps
    1. Frontend allows user to supply values for fixed set of params
    2. Frontend sends to backend
    3. Backend uses values as params in cf push command
• Allow users to view, edit and add to existing manifest file
  • A lot more steps..
    1. Fetch manifest from repo/remote url in backend
    2. Backend sends manifest to front end
    3. Front end displays manifest and allows edits
    4. Front end sends updated manifest to backend
    5. Backend replaces previous manifest with new
  • How do we redeploy with the same settings?
• Allow users to supply fields that can be added the manifest
  • Fewer steps
    1. Frontend allows adding any type of param
    2. Frontend sends to backend
    3. Backend fetches git repo and then updates manifest
  • How do we redeploy with the same settings?

If we store override values in stratos env var, ensure that we then resend them on redeploy

from stratos.

Implemented in #2924

from stratos.