Re: Environment variable changes in DIEGO
Mike Heath
By the `application_uris` data are broken logic, VCAP_SERVICES is also
broken and should be removed as it doesn't reflect service binding changes. In my (strong) opinion it doesn't make any sense to run an application in a dynamic environment and NOT expose its route(s). This has a lot of implications. For example, an application running on Diego can no longer register itself with a dynamic service registry since the information needed to route to the application is totally obscured. (i.e. Spring Cloud's integration with Eureka.) It makes more sense to me to match the behavior of service bind/unbind by notifying the user at route map/unmap time that they need to restart their app for it to see the changes. -Mike On Wed, Sep 16, 2015 at 9:09 AM Matthew Sykes <matthew.sykes(a)gmail.com> wrote: The changes, in general, were intentional. The `application_uris` data was |
|