Ops file use-metric-store does not set nats properties in the route_registrar job

[ctlong]

What is this issue about?

operations/use-metric-store.yml is failing in pipelines. The error appears to be related to a lack of NATs properties set in the route_registrar job.

cf-deployment/operations/use-metric-store.yml

Lines 82 to 94 in 6e06b9d

	- name: route_registrar
	properties:
	route_registrar:
	routes:
	- name: metric-store-reverse-proxy
	port: 8083
	registration_interval: 20s
	server_cert_domain_san: metric-store.((system_domain))
	tls_port: 8083
	uris:
	- metric-store.((system_domain))
	- '*.metric-store.((system_domain))'
	release: routing

What version of cf-deployment are you using?

v20.2.0

Please include the bosh deploy... command, including all the operations files (plus any experimental operation files you're using):

bosh deploy cf-deployment.yml -v system_domain=blah.example.com -o operations/use-metric-store.yml

Please provide output that helps describe the issue:

Task 35 | 13:10:07 | Preparing deployment: Rendering templates (00:00:22)
                   L Error: Unable to render instance groups for deployment. Errors are:
  - Unable to render jobs for instance group 'metric-store'. Errors are:
    - Unable to render templates for job 'route_registrar'. Errors are:
      - Error filling in template 'registrar_settings.json.erb' (line 55: undefined method `map' for nil:NilClass)

What IaaS is this issue occurring on?

GCP

Is there anything else unique or special about your setup?

There are some other ops files deployed but I don't think they're important.

Tag your pair, your PM, and/or team!

N/A

[ctlong]

The update-releases pipeline uses ops files that are in the release-candidate branch of CF-D. So the updated use-metrics-store ops file won't take effect in the pipeline, and allow the new version of the metric-store-release to be pulled into CF-D, until a new CF-D release is cut.