Add --check parameter to `virtualmin list-custom`

Submitted by yngens on Mon, 08/14/2017 - 07:34

The https://www.virtualmin.com/documentation/developer/cli/modify_custom for virtualmin modify-custom command states:

You must also supply the --set parameter at least once, which has to be followed by the code for the field to update and the new value.

However, there is no Virtualmin CLI command to do the opposite action - to check the previously set value. Would be nice to introduce the new --check parameter to virtualmin list-custom command like:

virtualmin list-custom --domain $dom --check custom-fields-name
Status: 
Closed (fixed)

Comments

Submitted by JamieCameron on Tue, 08/15/2017 - 00:52

Actually, there is a list-custom API command that can display custom fields for a domain.

Submitted by JamieCameron on Tue, 08/15/2017 - 00:53

Status: Active » Fixed

Submitted by yngens on Tue, 08/15/2017 - 05:00

Status: Fixed » Active

Jamie, please read my request once again. I know about the list-custom command, but it lists all the custom fields with their values, and I am suggesting a new command option to check the value of any given custom field.

Submitted by JamieCameron on Tue, 08/15/2017 - 10:46

What do you mean by check though? Validiating the field, or just displaying its contents?

Submitted by yngens on Tue, 08/15/2017 - 13:58

Displaying the value of one particular custom field. Because there could be lot's of custom fields and if there is a way to modify single fields value with virtualmin modify-custom why not to provide some way to display a single field value?

The list-custom operates all the fields at once and if you have bunch of custom fields you really do not want to list them all and then iterate through them to preg a value of just one of them.

Submitted by JamieCameron on Tue, 08/15/2017 - 17:59

Ok, I see what you mean - I will add flags to the list-custom API command to make this possible.

Submitted by JamieCameron on Tue, 08/15/2017 - 17:59

Status: Active » Fixed

Submitted by IssueBot on Tue, 08/29/2017 - 18:07

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.