You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is this check for API version > 2.14 for async unbind operations which fails the request when accepts_incomplete is true.
accepts_incomplete is not supported in versions <14, so I understand the point of the check.
However, in my use case, the broker is now deployed on K8S and the Service Catalog sends an async request with API version header 2.13. The service catalog uses the kubernetes-sigs/go-open-service-broker-client package and here we can see it uses the default configuration of the client lib, where the latest API version is 2.13.
I've also noticed that the check is not executed for deprovision, which is inconsistent.
What do you think about removing the check for now and rely more on the value passed as accepts_incomplete? If you agree, I can make the PR.
The text was updated successfully, but these errors were encountered:
Hello all,
There is this check for API version > 2.14 for async unbind operations which fails the request when
accepts_incomplete
istrue
.accepts_incomplete
is not supported in versions <14, so I understand the point of the check.However, in my use case, the broker is now deployed on K8S and the Service Catalog sends an async request with API version header
2.13
. The service catalog uses thekubernetes-sigs/go-open-service-broker-client
package and here we can see it uses the default configuration of the client lib, where the latest API version is 2.13.I've also noticed that the check is not executed for deprovision, which is inconsistent.
What do you think about removing the check for now and rely more on the value passed as
accepts_incomplete
? If you agree, I can make the PR.The text was updated successfully, but these errors were encountered: