Could be implemented an ovirt-shell command like 'set' to set configuration from ovirt-shell and save it. Example: > set username = "foo@domain" > save -a # save all runtime settings 3. Aliases like in lftp client? > alias lsvmmyvm list vms --query "name=myvm*" > save alias lsvmmyvm Actual results: Changing configuration of ovirt-shell is right now possible via editing config file on filesystem directly or to invoke ovirt-shell with specific arguments. Expected results: Defining alias/set and then save them from ovirt-shell would allow a user to save configuration without need to have direct access to config file. Additional info: Original discussion on the list: http://permalink.gmane.org/gmane.comp.emulators.ovirt.user/5374
(In reply to comment #0) > Could be implemented an ovirt-shell command like 'set' to set > configuration from ovirt-shell and save it. > > Example: > > set username = "foo@domain" > > save -a # save all runtime settings > > 3. Aliases like in lftp client? > > alias lsvmmyvm list vms --query "name=myvm*" > > save alias lsvmmyvm this can be achieved via scripting interface, see [1]. [1] http://www.ovirt.org/CLI#Scripting > > Actual results: > Changing configuration of ovirt-shell is right now possible > via editing config file on filesystem directly or to invoke > ovirt-shell with specific arguments. > > Expected results: > Defining alias/set and then save them from ovirt-shell > would allow a user to save configuration without need to > have direct access to config file. > > Additional info: > Original discussion on the list: > http://permalink.gmane.org/gmane.comp.emulators.ovirt.user/5374
This, 'set' command to define/save configuration from ovirt-shell is useful, even more if BZ04939 would be implemented and users would have no access to filesystem to edit config and/or would not be allowed to define command args for ovirt-shell session.
Sorry typo, talking about BZ904939 of course.
Closing old bugs. If this issue is still relevant/important in current version, please re-open the bug.