Alexander Guschin
Alexander Guschin
For rerun, we could simply check that the command (`mlem deployment run heroku app.mlem --model models/clf-model --app_name bank-churn-app`) is going to create exactly the same file => it doesn't change...
> a re-run of the command should guarantee the same result (idempotent) > I would personally expect the "--force" behavior to be the default behavior Good point, thanks for sharing...
In general, sounds totally logical to me. > 4. Deployment was not complete with different params - ??? probably error out unless --force? I think the behavior should be the...
After some thinking, let's allow `--force` option for items 5 and 7. In the case of 7 (Deployment already existing with different params), let's first do `mlem deploy remove` and...
Sounds logical to me. Could be an option, but we already have `mlem deploy apply` that relates to getting predictions from that deployment using data at hand (which is a...
Sorry guys, missed this. If the underlying implementation doesn't look too heavy for @mike0sv, I agree we can rename `mlem apply` to `mlem infer` (or `mlem call`) and implement `deploy...
Let's do this and close the issue @mike0sv
@mike0sv do you have any ideas why this could be the case?
I assume this happens when trying to load the model. Looks like MLEM does not pin down this requirement when recursively going over the `model` at saving, I guess we...