model_id is mandatory for model queries but it can have any values

[bdattoma]

in order to query a model using caikit+TGIS runtime, we must pass the model_id parameter in the HTTP payload (or mm-model-id for grpc).
However, it can have any value and as far as the endpoint is correct, the model responses.

In the following screenshot you can see 3 calls:

1. first one using the actual model id
2. second one using a dummy model id
3. third one without the model id parameter

[Xaenalt]

Interesting, this should be a Caikit... bug...? That does indicate some weirdness in the finder for the models, but I'm not sure this is a big problem with how we use the Caikit component here xD

[bdattoma]

@Xaenalt @dtrifiro what should we do with this ticket?

[dtrifiro]

We can keep this open for now

[Xaenalt]

Let's keep this open for now, I'm not sure what the intended behavior is
@gabe-l-hart @gkumbhat @evaline-ju

[gabe-l-hart]

Thanks for pointing this out! In general, caikit.runtime is designed to be a multi-tenanted server, serving multiple models per instance. For that reason, the id is required. The reason this is "working" with random ids had to do with how models are lazily discovered. With the TgisAutoFinder, any unknown id will act as a shim to TGIS.

There are a couple of things we can do to make this better:

• Limit the model ids allowed through the TgisAutoFinder so only the "right" id works
• Explore a default model id that gets used when none is present in the request

[bdattoma]

• at gets used w

thanks for the explanation Gabe.

What about setting the desired behavior with an Env variable? maybe for someone having the lazy discover of the model is a desired feature. In that case, the parameter could be make optional, for example