Thanks for replying, but I'm not sure I understand your instructions. I'm not sure what "check the route registrar merge" means. Do you mean that I should change the last 2 lines in

Regarding z2 number of instances are 0 so it is same as having just 1 zone. For login route error , route registrar on uaa job is adding login.10.60.18.186.xip.io to routes but from cloud controller

Hi Brian, The scopes that end up in the access token are the intersection of the client scopes and the user scopes. Which oauth client have you configured your spring cloud application with?

It seems to have generated two of them even through I am not using 2 zones. Also I see port 8080 mentioned somewhere in there, as mentioned before port 8080 is only opened internally in the security

Eyal , In your final manifest , can you check what are the properties under route-registrar for uaa job ? https://github.com/cloudfoundry/cf-release/blob/master/templates/cf.yml#L194

Has anyone implemented (and has some sample code/OSS project) for a service broker implementation to emit logs/events back into dopplr for each service binding's app? Nic

Hello All, Brand new to Cloud Foundry. I have hooked up a Spring Cloud Application to a UAA server and gotten it to authenticate properly. However, I noticed that none of the scopes that I defined in

That works, but now I cannot connect the cf client. I am getting a 404. It does not explicilty say so in the docs, so I assuming that the API endoint is: https://api.domain_for_haproxy_node is this

Hi Carsten, That's a good question. We haven't built anything specifically to support 0-downtime for the DEAs, but we have some upcoming changes to make the etcd used by etcd-metric-server,

You can replace it in the stub and rerun generate.

Can I replace it in the manifest stub and rerun generate? or do I need to replace it in the generated manifest?

Please try replacing all occurrences of "SYSTEM_DOMAIN" in your manifest with "sys.10.60.18.186.xip.io" and all instances of "APP_DOMAIN" with " apps.10.60.18.186.xip.io".

Following up on my previously posted config, I found the following message in /var/vcap/sys/log/cloud_controller_ng/cloud_controller_ng.log (The error log was empty... ): Problem is that I don't

Hello Ronak, I have used XIP. It does not seem to have helped. I got much the same result. API node does not complete the job. looking at the vcap logs looks similar to above: cloud_controller_ng_ctl

Ignore me, I can't read... looks like this is using that already. Nice!

Have we abandoned plans for the import path service Eric proposed back in April? If not, aren't we just going to have to update all our imports again once that rolls out?

Need more info. What's the command(s) you're running? What's the full output from the command(s)? What is the output of `cf target`? Is Diego supported / available on that target? Dan

I tried enabling the diego for the php app and I am not able to start the app after enabling. I get the below errors: Server error, status code: 500, error code: 10001, message: An unknown error

I got past the api_z1 failure by adding: - name: consul_agent release: cf to the api_z1 section. I'm now confused by having to remove the other lines. I will need to test this out. Tom

you can tell when you're on DEAs by comparing the notes that dan referred to here [1]. for example, if you have the env variable VCAP_APP_PORT then you're likely on a DEA