Fix Flow deployment of Model with float field (#6155)
When serving a Flow with HTTP, serving failed because the model reconstructed in the Gateway interpreted the float field as an array. Now the model served in the Gateway uses the correct schema.
Expose only /invocations endpoint when serving with --provider SAGEMAKER (#6152)
When exposing an Executor with SAGEMAKER as the provider argument, only the /invocations endpoint should be used. However, previously all other endpoints were also exposed. This is now fixed.
Optional parameters when typed parameter has all default fields (#6152)
When using a strongly typed parameters argument with the Executor endpoint, even if the parameters model type had all fields with default values and not required, you still needed to pass an empty parameters={} field to the call when serving via HTTP. With this change, you no longer need to pass this empty dictionary.
🤟 Contributors
We would like to thank all contributors to this release:
Release Note
This release contains 3 bug fixes.
🐞 Bug Fixes
Fix Flow deployment of Model with
floatfield (#6155)When serving a Flow with
HTTP, serving failed because the model reconstructed in the Gateway interpreted thefloatfield as an array. Now the model served in the Gateway uses the correct schema.Expose only
/invocationsendpoint when serving with--provider SAGEMAKER(#6152)When exposing an Executor with
SAGEMAKERas theproviderargument, only the/invocationsendpoint should be used. However, previously all other endpoints were also exposed. This is now fixed.Optional parameters when typed parameter has all default fields (#6152)
When using a strongly typed
parametersargument with the Executor endpoint, even if theparametersmodel type had all fields with default values and not required, you still needed to pass an emptyparameters={}field to the call when serving viaHTTP. With this change, you no longer need to pass this empty dictionary.🤟 Contributors
We would like to thank all contributors to this release: