toggle quoted messageShow quoted text
We have multiple foundries in our org and occasionally we would want to push an app in the stopped state to a pool for DR purposes (active/active across foundries is always desirable but simply not always practical for older applications transitioning to CF).
thanks to all that have replied.
i'd like to ask a clarifying question. it sounds like most of these use-cases are "set up some environment for the app". this implies to me that these workflows are for new apps and not for updating existing ones. does that sound right? are their use-cases for "no-start" when updating an app?
On Wed, Jun 27, 2018 at 4:30 PM Abby Chau <achau@...
Hey Bernd and Julian,
Many thanks for your responses.
Wondering if you folks have tried using the `v3-create-app` command as Mike has pointed out (and Zach elsewhere). The command is basically the equivalent of `cf push test --no-start` in that it creates an app, leaves it in a `stopped` state, and users can then apply configurations, bind services, set-groups, enable ssh, etc. This command appears to be a workaround for your use cases, but please let us know if that's incorrect.