Is your feature request related to a problem? Please describe.
Currently ServicePlans in the catalog allow for a "Cost" to be defined, and in the examples this is set to a simple URL for AWS pricing pages. However, some OSB compatible tools (i.e. Stratos) use a different convention for costs, as defined here:
The result of this is that no costs data is surfaced in such tools for the AWS Service Broker provided services.
As this convention uses the key "Costs" instead of the currently provided "Cost", it's possible to explicitly support both conventions.
Describe the solution you'd like
Add a compatible Costs definition to the AWS ServiceBrokers specific extension to the CloudFoundry template language with the same structure as the convention linked above, and pass that through to the catalog output.
Describe alternatives you've considered
One alternative would be to modify all other tools to use the Cost structure provided by this broker, but that's fairly obviously the wrong thing.
Additional context
Add any other context or screenshots about the feature request here.
Is your feature request related to a problem? Please describe. Currently ServicePlans in the catalog allow for a "Cost" to be defined, and in the examples this is set to a simple URL for AWS pricing pages. However, some OSB compatible tools (i.e. Stratos) use a different convention for costs, as defined here:
https://github.com/openservicebrokerapi/servicebroker/blob/v2.13/profile.md#cost-object
The result of this is that no costs data is surfaced in such tools for the AWS Service Broker provided services.
As this convention uses the key "Costs" instead of the currently provided "Cost", it's possible to explicitly support both conventions.
Describe the solution you'd like Add a compatible Costs definition to the AWS ServiceBrokers specific extension to the CloudFoundry template language with the same structure as the convention linked above, and pass that through to the catalog output.
Describe alternatives you've considered One alternative would be to modify all other tools to use the Cost structure provided by this broker, but that's fairly obviously the wrong thing.
Additional context Add any other context or screenshots about the feature request here.