Thanks for picking up on this again - I really appreciate that. Unfortunately, it looks like we will have to abandon Concourse CI under these circumstances, which is a shame as I have come to love this project.
From a cloud foundry customer perspective I would like to argue that it should definitely be possible to deploy concourse ci setup on top of a managed cloud foundry service
pause. I agree that workers are not stateless apps in the cloud foundry sense, but it would be great if there was a way to get this running.
Now I am in a position where I would have to setup my own bosh director on another, supported cloud service (which I can not do due to restrictions set by our clients) just to get concourse working. When deciding on concourse ci - one natural thought was of course - oh look it’s Cloud Foundry related, so it must be really easy to get this to run on Cloud Foundry. I guess I always ignored the role that the bosh deployment played at the time.
Well, lesson learned and time to move on.