Details
-
Bug
-
Status: Open
-
Major
-
Resolution: Unresolved
-
None
-
None
-
None
Description
Falcon client takes in extra parameters passed to it by user and shows results, although these properties are filtered before passing to api.
Instead CLI should throw error in such cases.
One use case is :
list operation does not use native scheduler property, but if I give the following command it gives expected result :
falcon entity -type process -list -properties falcon.scheduler:native 1 (PROCESS) native-1
In such cases user assume that scheduler is able to handle list operation too.
The same behaviour was shown by other falcon CLI operations.