Bug 885429
| Summary: | [RFE] Validation of inputs to rhevm-shell | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Ilia Meerovich <iliam> |
| Component: | ovirt-engine-cli | Assignee: | Juan Hernández <juan.hernandez> |
| Status: | CLOSED CANTFIX | QA Contact: | yeylon <yeylon> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 3.1.0 | CC: | acathrow, bazulay, ecohen, iheim, jkt, juan.hernandez, lpeer, oramraz, Rhev-m-bugs, srevivo, yeylon |
| Target Milestone: | --- | Keywords: | FutureFeature |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | infra | ||
| Fixed In Version: | Doc Type: | Enhancement | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2014-06-23 11:27:57 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | Infra | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 959740, 1006918 | ||
|
Description
Ilia Meerovich
2012-12-09 11:52:58 UTC
as all options in cli available via auto-completion, i'd say this is minor issue, but indeed has to be addressed at some point. Michael please take a look at this issue and see that auto completion is bogus too: https://bugzilla.redhat.com/show_bug.cgi?id=885635 (In reply to comment #2) > Michael please take a look at this issue and see that auto completion is > bogus too: > https://bugzilla.redhat.com/show_bug.cgi?id=885635 ilia, 1. mentioned BZ is NOT-A-BUG 2. even if it was, private issue on a single use-case doesn't make Comment 1 irrelevant. what is worse, since multiple ways are available, we will have to support all of them, if we don't want to break users' scripts. Better to cut down on the options and maintain a small set IMO (In reply to comment #4) > what is worse, since multiple ways are available, we will have to support > all of them, if we don't want to break users' scripts. Better to cut down on > the options and maintain a small set IMO Dan, no multiple ways are available, only non-existent options get ignored silently and this is an issue reported in this BZ, e.g: [RHEVM shell (connected)]# list clusters --max=-1 --max=-1 ignored as no such parameter 'max=-1' in sdk [RHEVM shell (connected)]# list clusters --max -1 valid '--max -1' option only ignored by the engine as -1 is a default there [RHEVM shell (connected)]# list clusters --max ignored by the api as value for 'max' wasn't specified [RHEVM shell (connected)]# list clusters --max000 --max000 ignored as no such parameter 'max000' in sdk [RHEVM shell (connected)]# list clusters --max000 --this_is_bug_or_feature --max000 ignored as no such parameter 'max000' in sdk --this_is_bug_or_feature ignored as no such parameter 'this_is_bug_or_feature' in sdk currently SHELL runtime is agnostic to option types, currently SHELL runtime is agnostic to option types, basically the reason for that is not strongly typed nature of python it is written on, however there is a way to overcome this limitation by documenting arguments types in the sdk *** Bug 959740 has been marked as a duplicate of this bug. *** |