Health Check Timeout is 600s max and not 180 about docs-dev-guide HOT 7 CLOSED

Or how about:

The timeout attribute defaults to 60, but you can set it to any value up to the Cloud Controller's maximum_health_check_timeout property. maximum_health_check_timeout defaults to 180, but your Cloud Foundry operator can set to any value.

Then consider deleting the note-- not relevant if this is for developers not operators.
http://docs.cloudfoundry.org/devguide/deploy-apps/manifest.html#timeout

from docs-dev-guide.

We have created an issue in Pivotal Tracker to manage this:

https://www.pivotaltracker.com/story/show/150563122

The labels on this github issue will be updated when the story is started.

from docs-dev-guide.

What do you mean with CF Push allows 600?

D:\Users\koperd\Downloads\bin>cf p hct -p t\n -t 181
Creating app hct in org dies-test / space dev as admin...
FAILED
Server error, status code: 400, error code: 100001, message: The app is invalid: health_check_timeout Maximum exceeded: max 180s

D:\Users\koperd\Downloads\bin>cf p hct -p t\n -t 180
Creating app hct in org dies-test / space dev as admin...
OK

from docs-dev-guide.

from docs-dev-guide.

The value seems server-side configurable. Which is probably why we avoided mentioning the value in cf CLI help output.
https://github.com/cloudfoundry/cloud_controller_ng/blob/674202f2dd6135f4acf91ed9b08416a5a5d8bcec/bosh/jobs/cloud_controller_ng/templates/cloud_controller_ng.yml.erb#L242

@animatedmax What's your approach with such cases for the docs? Maybe you'd like to add a note that the value is server-side configurable so could be different than 180?

from docs-dev-guide.

We can replace "the maximum configurable timeout is 180 seconds" with "the default maximum configurable timeout is 180 seconds" and add that "Your Cloud Foundry operator can set other values for these defaults."

from docs-dev-guide.

That sounds good to me, including deleting the note!

from docs-dev-guide.