base_resource_type_defaults does not start concourse if you set

[dohq]

Bug Report

• Concourse version: v6.7.1
• Deployment type (BOSH/Docker/binary): BOSH
• Infrastructure/IaaS: AWS
• Browser (if applicable): nop

The following can also be handy

Added the following ops-file to support the pull limit of dockerhub.

- type: replace
  path: /instance_groups/name=concourse/jobs/name=web/properties?/base_resource_type_defaults
  value:
    registry-image:
      registry_mirror:
        host: https://<<docker-proxy-url>>

The following errors are output in the concourse log

+ [[ vcap != '' ]]
+ chown vcap:vcap /var/vcap/jobs/web/config/env/CONCOURSE_TSA_HOST_KEY
+ chmod 0600 /var/vcap/jobs/web/config/env/CONCOURSE_TSA_HOST_KEY
error: invalid argument for flag `--base-resource-type-defaults' (expected flag.File): stat registry-image:/var/vcap/jobs/web/config/env/CONCOURSE_BASE_RESOURCE_TYPE_DEFAULTS_registry-image: no such file or directory

The content of bpm.yml looks like this, with a registry-image:/ prefix

CONCOURSE_BASE_RESOURCE_TYPE_DEFAULTS: "registry-image:/var/vcap/jobs/web/config/env/CONCOURSE_BASE_RESOURCE_TYPE_DEFAULTS_registry-image"

I want to see if the content of the ops-files is bad or a bug.