Right now we have a step called RegisterRemoteModel in our framework that correlates to the register_model API In ml-commons when a remote model is given. Currently we only support creating a remote model with a given connector ID. For example:
However, ml-commons also supports creating an internal connector inside the model itself through this API. We currently don't support this, example payload:
To satisfy what a connector object is, we can potentially refactor some of the code in the CreateConnectorStep so we don't have duplicates for the connector parsing.
Is your feature request related to a problem?
Right now we have a step called RegisterRemoteModel in our framework that correlates to the register_model API In ml-commons when a remote model is given. Currently we only support creating a remote model with a given connector ID. For example:
However, ml-commons also supports creating an internal connector inside the model itself through this API. We currently don't support this, example payload:
What solution would you like?
There can be two solutions for this, either we create a new step name called
register_model_with_internal_connector
/register_internal_connector
/register_internal_model
. Or we change theregister_remote_model
step to allow for either a connector ID or a connector object by changing the parsing method here: https://github.com/opensearch-project/flow-framework/blob/main/src/main/java/org/opensearch/flowframework/workflow/RegisterRemoteModelStep.java#L109To satisfy what a connector object is, we can potentially refactor some of the code in the CreateConnectorStep so we don't have duplicates for the connector parsing.