cost structure in existing spec is ill-defined about servicebroker HOT 5 CLOSED

The example in the spec has been updated, and we discuss in profile.md that cost is part of metadata and not defined in the spec.

api.md defines it as 'cost'
catalog-metadata.md defines it as 'costs'

The AppDirect broker uses costs, and this is used in the PWS web UI.

the structure of the 'cost' object is defined in terms of usd, which is obviously somewhat centered on a specific currency. As well as using that currency as a key in an object, which is not good.
It is unclear about how multiple costs combine together if they exist.

Though there are likely better schemas; the current one used by Pivotal does allow for multiple currencies:

"costs": [
  {
    "amount": {
      "usd": 649.0,
      "yen": 1000,
      "euro": 700
    },
    "unit": "MONTHLY"
  }
]

I would say we close this and if someone would like to see costs defined in the specification, they should open a new issue.

from servicebroker.

This is a relevant point for us because being able to display a service cost is a requirement of one of our customers.

I agree that we should do a pass on the spec and refine the current definition. It is in our TODO list but right now it is low priority so we haven't started working on it.

from servicebroker.

I believe the issue @MHBauer is referring to is only that the example in the api spec doesn't match the suggested field in http://docs.cloudfoundry.org/services/catalog-metadata.html.

I believe it's reasonable to update the example in the api spec to match, if it removes some confusion. It doesn't change the spec, as this field is not in the spec.

I'll include the change with my PR to migrate the spec from CF.

from servicebroker.

@shalako I believe this bug is resolved. Would you or @MHBauer like to confirm and close this issue? Thanks

from servicebroker.

Current spec and such seems fine now.

from servicebroker.