[CLI] everestctl install does not recognize the option to install the operators

Description

Even selecting a specific operator in the question:

It is still installing all operators:

Environment

None

Attachments

1

Activity

Show:

Oksana Grishchenko June 19, 2024 at 7:48 AM

the skip-wizard flag still makes sense if the user wants to use the default values and doesn’t want to provide any flags. For that they would could run:

everestctl install --skip-wizard

Manish Chawla June 19, 2024 at 7:34 AM

Cli version

If namespaces flag is given, then the cli will take that value and will not ask it again in the wizard

If the flags and values for both namespaces and operators is given, then the cli proceeds with the installation and wizard is skipped automatically

Maybe the --skip-wizard flag is not required now and can be removed.

Oksana Grishchenko June 11, 2024 at 9:09 AM

Notes for QA: what’s changed

Now the flags have priority over the wizard. If the user provided flags for namespaces and/or engines, they’re not going to be asked for it again in wizard.

Oksana Grishchenko May 28, 2024 at 10:33 AM

UPD: Please disregard the previous comment, we’ve figured out the problem is that the flags are conflicting with the wizard and we need to address that. Thank you for creating the ticket!

Oksana Grishchenko May 28, 2024 at 10:03 AM

Couldn’t reproduce the scenario, the selector works as intended.

I would assume that the problem appeared because of a misusage of the CLI. Attaching a screenshot with a correct usage. I think the confusion appeared because on the step 2 the the user had navigated to the desired operator and hit Enter (instead of hitting Space as the cli hint suggests), which is interpreted as “proceed with the selected options“ whereas all the operators were selected, so they all were installed.

could you please confirm that it was the case? Since the wizard is confusing we may need to discuss and rework it.

Done

Details

Assignee

Reporter

Fix versions

Priority

Smart Checklist

Created February 28, 2024 at 11:47 PM
Updated July 1, 2024 at 9:23 AM
Resolved June 19, 2024 at 7:34 AM