-
Notifications
You must be signed in to change notification settings - Fork 44
CLI: too many -c
arguments without enough detail about what's required
#233
Comments
related to #214 |
We have |
Where can we find a list of all possible config options per command? I was pointed to https://github.com/iterative/mlem/blob/main/tests/contrib/test_heroku.py before but it's unclear what the config options are in there. |
@mike0sv, could you please answer the Jorge's question? |
you can run |
Agree: iterative/mlem.ai#143 Documenting all existing config options may also help us design a more segmented config CLI later (for this issue). |
closed by #363 🎸 |
Examples from the docs:
$ mlem pack rf pip -c target=build/ -c package_name=example_mlem_get_started
$ mlem apply-remote http test_x.csv -c host="0.0.0.0" -c port=8080 --json
$ mlem create env heroku staging -c api_key=<you api key>
$ mlem create deployment heroku myservice -c app_name=example-mlem-get-started -c model=model -c env=staging
$ mlem apply-remote http test_x.csv -c host=http://my-mlem-service.herokuapp.com -c port=80 --json
It feels like
-c
is being used as a catch-all and a way to avoid specifying the actual expected options for each command. It's not clear what each-c
option is doing (if anything), which ones are required, and what values are expected.The text was updated successfully, but these errors were encountered: