cloudfoundry-community/bosh-config-resource

Concourse resource for bosh cloud/runtime config

bosh-config-resource's Issues

Use the same source param names as the bosh-deployment-resource

https://github.com/cloudfoundry/bosh-deployment-resource#example

this would allow using yaml pointers which avoids duplication.

watch a collection of configs instead of a single one

By specifying a pattern for config types and names, collecting them in a set order (ie alphabetical or numeric id), then comparing the sha sum of the conglomerate, the pipeline can pick up addition or removal of configurations, not just changes to specific configs. This is important for handling multiple named runtime configs where each config is defined for its purpose, for example.

Pattern could be something like 'cloud,runtime@*', which would detect only the default cloud config, and all runtime configs, but no cpi configs.

Support dynamic BOSH Director config

The README says that target_file is supported as an out parameter, but I can't see any use of it in the code.

It'd be really rather lovely if it supported the same configuration style as https://github.com/cloudfoundry/bosh-deployment-resource

Can 'ca_cert' be made optional?

In scenarios where the BOSH director is deployed with a certificate that's already trusted by the system cert pool, I shouldn't have to specify it. We're using a certificate issued by a root CA, and having to go and get the CA certificate is a little awkward.