cloudfoundry/cf-release — pull request #275 by wdneto (2014-01-31 01:28:15+00:00)
Title: Move property defaults to job spec file instead of within ERB templates

Hi Guys,

Just noticed that some properties were being defaulted inside ERB code, instead of leveraging the job spec file.

Figure it'd be best to have them on the spec instead, so a documented manifest can be easily formed from the spec files.

Looking through the remainder of the code using something like:
```
grep -HR --only-matching --perl-regexp "..p\(('|\")[A-Za-z0-9 \._-]+('|\"),[A-Za-z0-9 \._-]+\)" *
```
Did not reveal any other use cases.

I also chose to rename the property to ccng.* instead of router.* as router.* didn't seem to be used anywhere else (in particular, not even on the router job). I assume this is left over from prior to switching between nginx/gorouter.