cloudfoundry
Allow max-timeout for async-binding larger than 60 seconds, via "cf push command"
Hello all, This is an enhancement request
Issue
Allow max-timeout for async-binding larger than 60 seconds, via "cf push command"
Context
The current behavior of bindings which are created on the fly via "cf push" command according to manifest file, is that in case a single binding does not succeed in 60 seconds, the push command fails. Typically, async-bindings are used where the binding logic takes more time by default. Therefore one can expect, than once we implemented async binding exactly due to this reason, is that it can be supported via "cf push" command, and the binding timeout can be extended beyond 60 seconds.
A reasonable approach can be to set a max-timeout on the app-deploy level (with a hard coded upper bound), and to be able to extend the push operation up to this timeout.
Steps to Reproduce
implement dummy broker which holds the request for more than 60 seconds & returns success afterwards. state binding to this instance via manifest yaml to some hello-world app exeucte cf push command
Expected result
push command will succeed
Current result
push command fails
Hello Colleagues - Any news regarding this ? Its very strange that we can implement async behavior for binding - but we are limited with 60 seconds for overall execution with the most common production-grade cf deployment such as "cf push" with blue-green strategy
