`cf cups` == `cf create-user-provided-service`
`cf uups` == `cf update-user-provided-service`
First off - thanks for the new `cf uups` command. It may be potentially nicer than deleting/re-creating user-provided services when the property needs to change - I've not used it in anger yet, so ... who can say. :-)
One thing that's different between cups and uups is that with cups I can pass a list of property names in with the `-p` option, but with uups I can ONLY pass a string of JSON. I find the "pass a property list" style option is super easy - and so I think it probably makes sense for uups as well. Presumably you could pass new properties, or replace the value of existing properties.
Then we need one more thing - `cf ups` == `cf user-provided-service` - to get the property values of existing user-provided services printed to stdout. The "command naming standard" seems to be that "view"-ish functions have no verb prepended, otherwise I would have suggested "vups - view-user-provided-service".
Today I find myself binding a ups to a kinda dummy app I have lying around, then doing a `cf env` on it - but is obviously more work than I'd like to do.
--
Patrick Mueller
http://muellerware.org