Re: BOSH Manifest and directory_uuid


Dmitriy Kalinin
 

It's a safety feature so that people do not accidentally deploy deployment
with a same name to a wrong environment. For example if you have staging
and prod environments and both have cf deployment.

On Wed, May 20, 2015 at 10:30 AM, albertoaflores <aaflores(a)gmail.com> wrote:

Team,

After reviewing the bosh.io site and other email list, I can't find a good
reason on why does the manifest YAML file needs to have the director_uuid
in
the manifest. According to the docs found here:

http://bosh.io/docs/deployment-manifest.html#deployment

It is a "required" field. Is this so? Keeping manifests in version control
will create a dependency on a single Director running. Is this by design?
Just looking for clarification more than a rant... :)



--
View this message in context:
http://cf-bosh.70367.x6.nabble.com/BOSH-Manifest-and-directory-uuid-tp45.html
Sent from the CF BOSH mailing list archive at Nabble.com.
_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

Join cf-bosh@lists.cloudfoundry.org to automatically receive all group messages.