cloudfoundry/nfs-volume-release

Add documentation binding service through manifest

farahfa opened this issue · 4 comments

Hello,

The documentation is great for setting things up and getting started, but I think it would be nice if you guys add to your documentation how to bind the nfs service using a sample manifest file.

For example:

cf bind-service pora nfs_test -c '{"uid":"1000","gid":"1000","mount":"/dir"}' <-- How would that be done in a manifest file?

Thanks

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

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

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

@farahfa thanks for pointing this out. We should definitely update our docs.

In the mean time, what you are trying to accomplish is sort of possible...the cloud foundry runtime doesn't support setting service binding configuration through an application manifest, so you have to bind to the service without configuration. In order to make that work, you have to specify the binding parameters upfront when creating the service instance. (binding parameters can also be specified when creating the service instance, provided that you are using the very latest code.)

The only caveat I'd add is that because we don't store service instances encrypted in the broker data store, you should avoid setting LDAP username/password during service instance creation. We have some stories in our backlog to fix that before we cut our next release.

How "latest" is latest? Latest of which component? We're trying to do just this and getting "Service broker error: Unexpected end of JSON input".

$ cf version
cf.exe version 6.35.1+bfbe5f0e8.2018-03-14
$ cf api
api endpoint:   https://api.cf-prod.intranet.rws.nl
api version:    2.103.0

Update: the relevant version is the version of nfs-volume-release in our BOSH deployment—1.2.0, which does not contain the code to pass through NFS options from the service creation.