-
Notifications
You must be signed in to change notification settings - Fork 436
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
Ability to declare schema of binding credential output #116
Comments
@bmelville is there any documentation on how the schema works that I can look at? |
Since binding is a generic operation itself, the output is arbitrary. Therefore if we schematise the whole output, we will cover this use case (credentials) plus any other possible scenario. |
I have an initial proposal for this: https://docs.google.com/document/d/1JbsJgqgNtqthcfYwK_KbS6C8sjElrZNgoLhu40dUPAs/edit?usp=sharing It contains two separate potential proposals. |
From 11/12 call, @n3wscott will write-up a proposal |
Should this issue be in validating-through-implementation now that #392 is in that state? |
We spoke about this on today's OSBAPI weekly call. We think that a proposal similar to the A proposal like this would provide a couple of benefits:
We are waiting for an owner to volunteer to pick this one up, as we are currently tied up with the Extensions work. |
Our group in SAP is currently working with CF and k8s brokers. Some of the brokers we use provide IaaS native AWS, GCP and Azure services. Credentials for the same backing service (PostgreSQL for instance) might be slightly different: We see a structured way to handle credentials (schema) as a way to solve the above issue. |
Binding credentials are a generic map of data, and as such are difficult to reason about or program against in a meaningful way. Similar to issue #59, we would like to support the ability to declare the schema of credential outputs from a binding.
Proposal: https://docs.google.com/document/d/1JbsJgqgNtqthcfYwK_KbS6C8sjElrZNgoLhu40dUPAs/edit?usp=sharing
The text was updated successfully, but these errors were encountered: