Add ability to override deployment name

[fbonelle]

For our migration from v25 to v26, we had difficulties with deployment name hard coded. This patch adds the ability to set a personalized deployment name. The property property_overrides.deployment_name does not have to be defined (in this case, it's like the old behaviour).

[cfdreddbot]

Hey fbonelle!

Thanks for submitting this pull request! I'm here to inform the recipients of the pull request that you and the commit authors have already signed the CLA.

[cf-gitbot]

We have created an issue in Pivotal Tracker to manage this. You can view the current status of your issue at: https://www.pivotaltracker.com/story/show/117225385.

[mfine30]

Hey @fbonelle,

This looks like a useful change for anyone who does not want to use the hardcoded deployment name and still use the manifest generation scripts included in the repo.

One thing that we would like to see in this commit before we merge it is the corresponding update to the manifest-generation/examples/property-overrides.yml file so that contributors and users of the release understand how to modify that property, similar to property_overrides.host.

Thanks,
Morgan
CF Core Services

[fbonelle]

Hi,
I have done what you asked for.
Regards

[menicosia]

Hi @fbonelle,

Thanks! I'll prioritize this for the team to try to pull into the next release. You can follow the story's progress in our backlog, hopefully this will land in cf-mysql v27.

Marco Nicosia
Product Manager
Pivotal Software, Inc.