 |
Oleg Shaldybin |
at Jul 12, 2012 at 2:29 am
|
⇧ | 
| |
We are working on this feature right now. Job specs will be used to define
properties, and later during deployment complete property validation will
be performed, essentially giving a user list of properties that are missing
from the deployment manifest along with their type/description.
On Wed, Jul 11, 2012 at 7:06 PM, Brian McClain wrote:Agreed, I had been kicking around the idea of a tool that scans a BOSH
release to determine valid/required properties, but not quite sure it's the
best route.
I've got nothing else to add, but I agree Nic, this is an important piece
Brian
@brianmmcclain
On Wednesday, July 11, 2012 12:41:13 AM UTC-4, Dr Nic Williams wrote:Each time I see a patch to bosh-release [1], cf-release, etc I am
reminded that we're not getting any closer to a culture of documenting that
the available properties are for bosh releases.
I've poked around a few times with example ideas, but haven't come up
with any syntax or documentation I like yet.
Anyone else have ideas on how we could document what properties are
available for releases (or combinations of properties)?
[1]
http://reviews.**cloudfoundry.org/#/c/6948/1/**jobs/director/templates/**director.yml.erb<
http://reviews.cloudfoundry.org/#/c/6948/1/jobs/director/templates/director.yml.erb> -
added properties.director.encr**yption
------------------------------
Dr Nic Williams - VP Developer Evangelism
[image: Engine Yard]
The Leading Platform as a Service
Mobile: 415 860 2185
Skype: nicwilliams
Twitter: @drnic
------------------------------
--
Best,
Oleg
