Enhanced Autocomplete CMK

[Imvedansh]

Hi everyone,

As part of my efforts to improve the autocompletion experience in CloudMonkey CLI, I’m currently working on identifying enum-based API parameters that are not currently auto-suggested but could significantly enhance usability if they were.

While CloudMonkey already handles dynamic parameters like zoneid and networkid via list APIs, many static or enum-style parameters (e.g., provider in createStoragePool) are not suggested due to lack of metadata exposure from CloudStack.

If you’ve run into parameters where you've had to guess or refer to docs often, I’d love to know — it’ll help prioritize which ones to focus on first.
#10442
Thanks in advance for your input!

regards,
Vedansh Singh

[DaanHoogland]

@Imvedansh, imho there are several different Status enum classes. I would focus on those first.

[Imvedansh]

@DaanHoogland Thank you for your response,
Can you elaborate a little please,
Which files are basically providing this functionality.
So far i went through https://github.com/apache/cloudstack-cloudmonkey
completer.go, config.go,api.go..
I understand well, how cmk fetches dynamic data ,with listapi's

[DaanHoogland]

I meant
com.cloud.host.Status
com.cloud.storage.Upload.Status
org.apache.cloudstack.backup.Backup.Status
org.apache.cloudstack.jobs.JobInfo.Status
com.cloud.storage.template.TemplateDownloader.Status
etc.

Not an exhaustive list but I would focus on those first.

[DaanHoogland]

also just my not so humble opinion. Feel not bound by it.

[Imvedansh]

Thanks a lot, @DaanHoogland

I’ll start by digging into the Status enums you mentioned and see how they’re structured and exposed. Definitely a solid direction to begin with, and your opinion is very much appreciated (humble or not 🙂).

If I run into anything odd or worth discussing further, I’ll follow up here.

Cheers!
Vedansh

[Pearl1594]

Some other useful and not so straightforward parameters in APIs that can be exposed include: Network service providers, storage providers - for storage Pools as well as image stores(secondary storage). A pointer would be to look into the ApiConstants.java file - and check in there for parameters used in APIs that are not supported by auto-completion.

[Imvedansh]

Thanks a lot for the pointers! I’ll dig into ApiConstants.java and start mapping out those missing autocompletion cases—especially around storage and network providers.

Appreciate the insight!