cloudfoundry-community
current_app_name behavior loses environment variables
When the zero-downtime deployment is triggered by the current_app_name property, it does not transfer over the environment variables that were set on the currently deployed app. This results in loss of any environment variables which were set via cf set-env rather than by the manifest or pipeline.
One could say that this is by design, however it runs counter to the cf push behavior, which maintains any currently set environment variables that are not present in the manifest.
One could say that this is by design
If it is then it seems odd. Why would rolling deployments not keep the env vars, whereas non-rolling deployments do. If it is 'by design' it would seem more logical to have both cases work the same way.
