Feature Request

What challenge are you facing?

Currently, the only way to pass data between jobs is using resources, which requires writing data to some external resource such as s3 or git repo. This is very handy and understandable to pass along big data and file structures.
I was surprised to realize that if you want to pass some key values form one job to another is unfeasible. For example, in the spring-cloud-pipelines project, they pass the current version using a github branch with one file and each worker needs to clone it locally just to get a hold of a simple string value that represents the version.
I think it is only natural to allow to pass out a set of key values between jobs, reducing the redundancy of having to have a resource just for it.

A Modest Proposal

Create a new type of resource (File?) that gets in the put phase a file to send out to the get in the following jobs. The only thing is that this resource has no configuration as it is not connected to any external service but being handled only by the Conourse orchestrator.