We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
As a backing service broker author
Some fields have camelcase naming e.g. brokered_service_context_spaceName , some others have _ as separators e.g. brokered_service_context_space_guid
brokered_service_context_spaceName
brokered_service_context_space_guid
Introduce a new x_osb_cmdb_v2 param with better naming, see related #100
x_osb_cmdb_v2
Reproduced on version 1.5.0 -->
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Expected behavior
As a backing service broker author
Observed behavior
Some fields have camelcase naming e.g.
brokered_service_context_spaceName
, some others have _ as separators e.g.brokered_service_context_space_guid
Posssible approach
Introduce a new
x_osb_cmdb_v2
param with better naming, see related #100Affected release
Reproduced on version 1.5.0
-->
The text was updated successfully, but these errors were encountered: