-
Notifications
You must be signed in to change notification settings - Fork 33
New issue
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
Instructions/tests for running the service catalog in front of the broker SDK #19
Comments
Agree 100% with this. |
The ansible service broker has done work with getting a catalog to run with our broker. |
I'm sorry, I read this the wrong way. Making a way to deploy the catalog is not a goal for this repo - it will be impossible to keep up to date and we have far too many ways of orchestrating things already. It's already extremely easy to deploy the catalog onto k8s with helm, and we're working toward support for I initially read this as 'add instructions for how to register brokers built from this SDK in the service-catalog', which is a thing I want. |
I do want a conformance suite for the catalog, that is a goal, though not one of this project. |
closing this, opened #26 for the registration requirement. |
A service broker is intended to run behind a service catalog which adapts and passes on requests to perform the various actions such as provision and bind. It would useful to be able to test and verify that the broker developed using this sdk was successfully able to integrate with the catalog. To enable this it should be made simple to set up the catalog and register the broker with it. It would then be very useful to have a set of "black box" test that would execute against the broker and validate it was responding as expected. It would also be good if these tests were easy to extend and modify so that they could remain useful throughout the development process.
The text was updated successfully, but these errors were encountered: