Comments (3)
That PoC proposal seems to completely change the way the API currently work. How would we reconcile future instantiation with the current REST API? Would we have separate operations for create and instantiate?
Sounds like defining workflows, a more complex and refined use case of the API. I agree with @shalako that this functionality should be provided by a higher level component using the API as-is.
from servicebroker.
In order for bindings to be of any value, they must be able to model relationships between two service instances.
This strikes me as hyperbole. Does the K8 developer not have an application for which they are responsible? Despite not having an explicit service-to-service binding feature, the existing binding behavior has provided a great deal of value to CF end-users.
Service-to-service binding can currently be fulfilled in CF with a workaround using service keys and parameters. Developer wants to bind service 1 ("from") to service 2 ("to"). They would create a service key of service 2 ("to"). A service key is just a binding that isn't delivered to an app, and for which the developer can discover the details. They can then create/update service 1 ("from") with the data from service 2 in the parameters
field. Seems to me a marketplace controller could orchestrate this flow without any change to the broker API.
The top-level app_guid
field in the create-binding request should be considered a deprecated field, as we introduced bind_resource
to support fields the broker expects from the marketplace controller. For this use-case, it seems to me parameters
is more appropriate. A broker may or may not support configuration of a service instance that grants it access to another service.
from servicebroker.
This issue was created when the repo was geared toward both an open broker and controller spec. I agree that this is more of a controller feature, and does not strictly necessitate broker API changes to function (e.g., can use existing parameters field).
from servicebroker.
Related Issues (20)
- Update existing service instance: not able to delete while update in progress HOT 2
- Not Able to return 410 status code via get instance last operation call in async service broker HOT 1
- OpenAPI spec points to unsupported JSON schema definition
- In case of X-broker-api-version code and spec not working synchronously HOT 1
- Service to Service Binding HOT 3
- Mismatch in the response of last operation for service bindings in openapi.yaml
- OpenAPI / Swagger service plan resources are missing properties
- Swagger spec is missing service binding endpoint object + properties
- Video: What is the Open Service Broker API? is private HOT 3
- Inconsistencies between `ServiceBindingMetadata` and `ServiceInstanceMetadata` HOT 1
- Service broker API of version 2.16 is showing the stack trace instead of single error msg line which is revealing internal code details HOT 3
- Failed to evaluate Jackson deserialization for type [[simple type, class org.springframework.cloud.servicebroker.model.instance.CreateServiceInstanceRequest]]: com.fasterxml.jackson.databind.exc.InvalidDefinitionException: Conflicting getter definitions for property "organization_guid" HOT 2
- Conditional display or filtering of service plans on the OSB broker side HOT 1
- Orphan mitigation vs. still usable service instances after deprovisioning failure HOT 3
- Archieved Golang OSB Frameworks - Any new plan/replacement? HOT 1
- Response not specified when updating non-existing service instance
- Security Controls within the ServiceBroker API model
- Adding a new column in the existing table to indicate the default values for any specific field
- How to treat changing cost?
- Change open service broker configuration to clone cloud source repo using HTTPS instead of SSH
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from servicebroker.