Openstack, cf 230

Following a manifest for 225, routing-api is part of the api_z instance.
Generating the manifest for 230, routing-api is not included. Following on what worked, I added it. Api would not start.
routing-api failed:
{"timestamp":"1455647513.437552214","source":"routing-api","message":"routing-api.uaa-key-fetcher.fetch-key-started","log_level":1,"d
ata":{"session":"1"}}
{"timestamp":"1455647513.450663328","source":"routing-api","message":"routing-api.uaa-key-fetcher.http-error-fetching-key","log_level
":2,"data":{"error":"http-error-fetching-key","session":"1"}}
{"timestamp":"1455647513.450931787","source":"routing-api","message":"routing-api.uaa-key-fetcher.fetch-key-completed","log_level":1,
"data":{"session":"1"}}
{"timestamp":"1455647513.451057196","source":"routing-api","message":"routing-api.Failed to get verification key from UAA","log_level
":2,"data":{"error":"http-error-fetching-key"}}
{"timestamp":"1455647583.828899622","source":"routing-api","message":"routing-api.database","log_level":1,"data":{"etcd-addresses":["
http://192.168.20.19:4001"]}}

Removed routing-api. CF deploy works fine, all appears ok.
What features will I lose with this not being deployed? We have scripts make rest calls for routes. I haven't taken a crack at those yet.
Any additional pointers welcome.

Thanks,
Tom