If you pass --dry-run to a bkr workflow command it won't submit the job to Beaker. That means that it won't be making any calls to Beaker which actually require authentication. It may be useful to use bkr workflow-* --dry-run as part of some automation to produce a job XML definition, where the script is running under some account which does not have credentials to authenticate to Beaker. Currently the workflow commands will just fail during authentication to Beaker, but if --dry-run is given they should skip authentication and run unauthenticated to support this scenario.
Jeff Burke sent me a patch for this.
I realised there is a much simpler and more suitable solution here (and also less error prone)... We can add a bit of code which will just skip the authentication if your config has AUTH_METHOD="none". Then bkr will just proceed as normal, any calls which don't require authentication will succeed, and if you do try to do something which requires authentication like submitting a job you will just get an error saying "Anonymous access denied". It's a very unintrusive patch and it won't affect existing installations since it requires opting in by setting AUTH_METHOD="none". It also seems like the best option in this case, where there is a script running unattended and it has no Kerberos credentials. In that case there really is no possible authentication method to be used. Jeff, how does that sound to you?
http://gerrit.beaker-project.org/4780
This bug fix is included in beaker-client-22.4-0.git.6.5613dcf which is currently available for download here: https://beaker-project.org/nightlies/release-22/
Hi All, Do you know when a version of beaker-client will be available to be installed. Thanks, Jeff
At the moment we are not planning to do a 22.4 release since 23.0 is nearly ready. In the meantime you can grab the latest build from the release-22 nightlies repo mentioned in comment 4. Even though it's a git build, it's still identical to what would be released as 22.4 so it should be fine to use.
This patch was merged to the release-22 branch but the next release will be 23.0.
*** Bug 1214231 has been marked as a duplicate of this bug. ***
Beaker 23.0 has been released.