You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Refactor the tests so that we run more tests in interactive mode. This would significantly increase the speed of running the tests (most of the time for each test is pywbemcli startup). (issue Run more tests in interactive mode to reduce test time #949)
Consider a machine-readable form of output that would allow command redirection at least at the shell level. Note that click itself does not really support the idea of redirection in the interactive mode (output of one command available as input to the next command) but we could use the click context as a way to pass results to input in the interactive mode (Which would make the command mode different than the interactive mode). Some examples of usage might be: Run a command to get the namespaces and then run anther command on all of those namespaces.The easiest idea for this is the processing of things like connection names, instancenames, classnames, and namespace names. or lists of the same. (issue Machine-readable form of output for piping #951)
Indications: QUESTION/KS: How important are indications and subscriptions to pywbemcli. I do not know
Consider maintaining some information between commands in the interactive mode beyond what is maintained by the Server class. Remember that profiles and namespaces are maintained in the Server class instance as long as that object exists. ex. classes by namespace. Thus we would extend our pywbem_server to allow it to maintain more information. The information could include at least class names by namespace (partly addressed by issue Cache classes or at least classname retrieved from a server #483)
In the interactive mode consider maintaining connection information in memory when different connections are selected so that if a server was selected, any previous current connection would not be completely cleaned (today we clean each connection as it is selected). Some ideas are stash of class names or classes by namespace. Maintain the concept of a current thing; current class, current instance that would be applied to commands (partly addressed by issue Cache all information about an active server when switching connection #484)
For information:
Items for 0.9.0:
Ongoing items in each release:
Cleanup:
Testing:
Mock support:
Ease of use:
Namespaces:
Profiles:
Output formats:
Other:
Candidate items for after 0.9.0:
Cleanup:
Testing:
Ease of use:
Output formats:
Indications: QUESTION/KS: How important are indications and subscriptions to pywbemcli. I do not know
Maintaining server state in interactive mode:
Other:
The text was updated successfully, but these errors were encountered: