Hide Forgot
Description of problem: v7-1.5 needs to able to open a new cert from the command line of the SUT. Steps to Reproduce: 1. v7 {proper commandline with password} Expected results: A new cert/bug is created in parallel with the capabilities of enter.cgi without attachment.
Created attachment 561776 [details] the patch for xmlrpc
verified on web2
Created attachment 580384 [details] the new patch addressing make id
Created attachment 580393 [details] new Patch for make id
Is the user notified after the cert is opened with unknown vendor/make that they should go to the web UI to make the corrections? Some simple messaging between v7 and catalog is needed here likely. Greg, do you have any feedback for how this does or should happen?
(In reply to comment #22) > Is the user notified after the cert is opened with unknown vendor/make that > they should go to the web UI to make the corrections? Some simple messaging > between v7 and catalog is needed here likely. This is not included in the code, I have no idea how to implement this, maybe we can do this later.
I have adopted tfu's suggestion, change the return value of create method to a hash(dictionary in python), the structure will be { id => id-value, warning => warning-value}, if warning-value is not an empty string, v7 would print that warning value. e.g. data = s.Cert.create(params) data['id'] is the newly created cert's id if data['warning']: print data['warning'] What do you think, Rob, Greg?
Created attachment 581564 [details] new patch for adding warnings
verified on partner