Closed eriknelson closed 5 years ago
More generically, this begs the question, what is the best way to gate off experimental features of the OSB for users of this library, and allow them to opt into them based on their individual needs?
I ran into a similar problem with originating identity feature being disabled by default in the service-catalog. Have no good idea right now, just wanted to say 👍 on this discussion!
@LiliC Agreed!
I'm mostly interested in a strategy for this project to handle the experimental features of OSB. We care about async bind, but there will be interesting extensions that will continue to be submitted to the OSB group. It would be nice if broker authors could opt-in to these extensions in an API supported way. Please comment on my pitched PR, I wanted to also throw out a way to accomplish this and get some feedback.
Async Bind is not currently supported, which is an experimental spec feature the Automation Broker heavily depends on. We need a way to expose the necessary endpoints before we would be able to use the
osb-broker-lib
.More generically, this begs the question, what is the best way to gate off experimental features of the OSB for users of this library, and allow them to opt into them based on their individual needs?