Include support for bosh ops files

[orange-cloudfoundry]

Include support for bosh ops files

[poblin-orange]

convention could be:

xx-ops.yml
xx-ops-tpl.yml => standard spruce templating => xx-ops.yml => used as -o file in bosh cli v2 deploy / concourse resource.

xx-vars.yml
xx-vars-tpl.yml => standard spruce templating => xx-vars.yml => used as -vars file in bosh cli v2 deploy / concourse resource.

Question: ops-file might have an required order ? does alphabetic order apply ?

[gberche-orange]

Lack of documentation of path format in the resource, however example of wildcard into https://github.com/cloudfoundry/bosh-deployment-resource/blob/b8c1feafee9129644e5c4eccd42c1d1cddda8a00/ci/pipeline.yml#L162

About ordering of ops file and vars files when specified as a wildcard:

Seems the concourse resources uses the bosh cli code to resolve file path argument
https://github.com/cloudfoundry/bosh-deployment-resource/blob/master/bosh/director.go#L78
https://github.com/cloudfoundry/bosh-cli/blob/master/cmd/ops_file_arg_test.go

Did not yet find related code for wildcard expansion