Allow define new resource types from docker images in the pipeline manifest #250
To add new custom resource types, currently it is necessary to redeploy the job
For the tasks, instead, any new image can be defined in the manifest itself with the key
What I propose allow the pipeline definition to specify the docker image for resource directly, without requiring redeploy groundcrew job with bosh in concourse.
This would allow seamless use custom resources in any concourse installation, even in the vanilla concourse-lite, and make the pipelines more portable, as they don't have a dependency on the installed resources but can specify their own resources.
A pair of possible pipeline syntax can be:
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.
Building on #252, I think this'll look something like:
resource_types: - name: bosh-init-deployment image: type: docker-image source: repository: somethirdparty/bosh-init-deployment-resource resources: - name: bosh-director-deployment type: bosh-init-deployment source: # ...
All stories related to this issue have been accepted, so I'm going to automatically close this issue.
At the time of writing, the following stories have been accepted:
If you feel there is still more to be done, or if you have any questions, leave a comment and we'll reopen if necessary!