I'm the maintainer of the plain-content, file-based “keyval-resource” and as such , when I've seen your “keyval” resource recently in the Concourse Resource Types I've was very interested.
Turns out, your resource is very different from plain key-values, with the support for Bloblang documents.
Also, the key-values can only be created through params of the put: keyval steps. The original key-value resource aims at providing a file-based interface in artefact directories exposed to or filled from tasks executions.
In order to avoid any confusion in the Concourse community, would you accept renaming your resource bloblang-keyval-resource? This would help understand at first glance how it distinguishes from the “classical” keyval resources.
I'm available on Cloud Foundry Slack with my full name, if you need to reach out.
Always keen on chatting with other Concourse fans, hope to hear from you soon, thanks!
Hi @cludden!
I'm the maintainer of the plain-content, file-based “keyval-resource” and as such , when I've seen your “keyval” resource recently in the Concourse Resource Types I've was very interested.
Turns out, your resource is very different from plain key-values, with the support for Bloblang documents.
Also, the key-values can only be created through
params
of theput: keyval
steps. The original key-value resource aims at providing a file-based interface in artefact directories exposed to or filled from tasks executions.In order to avoid any confusion in the Concourse community, would you accept renaming your resource
bloblang-keyval-resource
? This would help understand at first glance how it distinguishes from the “classical” keyval resources.I'm available on Cloud Foundry Slack with my full name, if you need to reach out.
Always keen on chatting with other Concourse fans, hope to hear from you soon, thanks!