Your team recently added the ability to "loan-grant" and "loan-return" via beaker-client which has been a very useful addition. It would be helpful to the eng-ops labs and fls teams if we could also change a beaker systems "Owner" and "Condition" via beaker-client. -Keith Fryklund
This fits with the general theme of moving towards better support for using Beaker as a backend service platform rather than going through the main web UI, so ack'ing this one. I'm going to split it into two RFEs though, since the two commands can be implemented and tested separately. This one can cover change-owner, and I'll move the change-condition RFE out to a new one.
On Gerrit: http://gerrit.beaker-project.org/#/c/3251/
change-owner is not a great name for a subcommand, since it's not clear that it's changing the system owner. Also, to avoid subcommand proliferation and to match the existing job-modify, I suggest we do bkr system-modify FQDN --owner=USERNAME Similarly the other bug 1119930 would be bkr system-modify FQDN --condition=Broken
(In reply to Dan Callaghan from comment #4) > change-owner is not a great name for a subcommand, since it's not clear that > it's changing the system owner. Also, to avoid subcommand proliferation and > to match the existing job-modify, I suggest we do > > bkr system-modify FQDN --owner=USERNAME > > Similarly the other bug 1119930 would be > > bkr system-modify FQDN --condition=Broken Yeah, this sounds better. Also leaves the option for adding support for modifying other system attributes.
A system-modify subcommand sounds good to me.
http://gerrit.beaker-project.org/#/c/3251/
Beaker 19.0 has been released.