When bosh deploy fails the first time, there is no way to target that director and get the manifest it was trying to deploy. Given this is a concourse resource and not a bash script that we can modify and experiment with, every time the bosh deploy fails, we have to rekick the job from the beginning (and our job starts with a bosh delete-deployment so you can imagine this makes feedback loops rather long.) It would be great if this resource could print the manifest to a temporary location instead of forcing the user to hijack and try to recreate the bosh deploy command with all of it's arguments.
When bosh deploy fails the first time, there is no way to target that director and get the manifest it was trying to deploy. Given this is a concourse resource and not a bash script that we can modify and experiment with, every time the bosh deploy fails, we have to rekick the job from the beginning (and our job starts with a
bosh delete-deploymentso you can imagine this makes feedback loops rather long.) It would be great if this resource could print the manifest to a temporary location instead of forcing the user to hijack and try to recreate the bosh deploy command with all of it's arguments.cc @sophiewigmore