## Describe the bug On a failed bluegreen deployment, when the new app failed to start, cloudfoundry indicates to check the logs for more information. ``` TIP: use 'cf logs wrm-gateway-service-tmp --recent' for more information ``` But the template deletes the app as a bluegreen rollback thus it is impossible to access the logs and understand why the new app version failed to start. ## Expected behavior ~~The app new version (with the `tmp`) should not be deleted (may be changing the suffix to `tmp-failed`?).~~ The app new version (with the `tmp`) logs should be saved as artifact. ## Actual behavior The app new version is deleted and the logs are not available ## Logs and/or screenshots ``` .... Start unsuccessful TIP: use 'cf logs my-app-tmp --recent' for more information FAILED [ERROR] --- blue-green: failed deploying new app instance (see logs): cleanup Deleting app my-app-tmp in org my-org / space my-space as [MASKED]... ``` ## Context & Configuration The issue was reproduced using CloudFoundry template v1.1.0