-
Notifications
You must be signed in to change notification settings - Fork 63
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tail cf logs during staging when using blue/green deployment #28
Comments
Hi there! We use Pivotal Tracker to provide visibility into what our team is working on. A story for this issue has been automatically created. The current status is as follows:
This comment, as well as the labels on the issue, will be automatically updated as the status in Tracker changes. |
Is this bug being actively worked on? We might have interest in contributing if it's not already underway. |
AFAIK not, so I would hugely appreciate it. I'd be happy to assist as well if there's something I can help with (e.g. review, comment or giving you a free Cloud Foundry account to test it at meshcloud.io) |
@JohannesRudolph - if you want to try out the PR above: # Add to your list of resource types
resource_types:
- name: cf-resource-with-tail
type: docker-image
source:
repository: govau/cf-resource
tag: tail
# Change instances of cf-resource to cf-resource-with-tail, e.g.
resources:
- name: my-app
type: cf-resource-with-tail
source:
api: https://api.system.example.com
username: user
password: ((password))
organization: org
space: space
# Add show_app_log: true
jobs:
- name: job
plan:
- put: my-app
params:
manifest: manifest.yml
current_app_name: my-app
show_app_log: true |
Awesome, will give it a spin! |
@aeijdenberg worked a treat for me; just what I needed. Thanks! |
@drnic - if you liked that one, you might also want to look at contraband/autopilot#44 - we found it makes the deployment more robust (there were some corner cases in the old code). I'll ping the maintainers again about taking it upstream... seems to be pretty abandoned, which is a shame, as we've moved most of our delivery team to use it (well, our fork of it) for deployments for some time now. |
I was just bitten by not having cf logs available when using cf-resource together with blue/green deployments (specifying
params.current_app_name
). Because cf-resource deletes the staging app when staging fails, there's no way to recover these logs either.Proposed solution: cf-resource should connect to
cf logs current_app_name
and pipe the output to stdout until the app was successfully started.The text was updated successfully, but these errors were encountered: