Development Workflow for Resources

[michael....@gmail.com]

I'm wondering about an efficient workflow for developing (or patching) existing resources. At the moment we are building, exporting, tarring docker images. Making a new Bosh release and then deploy to our Concourse instance. This is a bit tedious :)

Is it maybe somehow possible to configure resources declaratively without having to bake them into a release? I'm thinking about just uploading the image to a registry and use them like tasks.

[surac...@gmail.com]

You can configure Concourse with docker URIs for the resource types, and then just keep pushing to the docker registry (or your own private one). Only gotcha is that auth is not supported, so your images would have to be public (or again on your own private registry).

We have plans to support a fly CLI -based workflow to "push up" resource types to the cluster (and guarantee the same image is used throughout the workers, etc). It'll take a while to get there though.