-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
EVA-3533 - Initial version of an orchestrator for submission processing #211
Conversation
|
||
def process_submissions(): | ||
|
||
scanner = SubmissionScanner() |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should this be NewSubmissionScanner
?
from retry import retry | ||
|
||
|
||
def _url_build(*args, **kwargs): |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe add a docstring stating that args
will be used as path params and kwargs
as query params
auth = (cfg.query('submissions', 'webservice', 'admin_username'), cfg.query('submissions', 'webservice', 'admin_password')) | ||
response = requests.put(url, auth=auth) | ||
response.raise_for_status() | ||
return response.json() |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is fine for the initial version but I would reiterate what I wrote in the second half of this comment about a client class for the submission-ws. This way all our Python code can use the web service uniformly, just configured using admin credentials when necessary.
Co-authored-by: April Shen <[email protected]>
No description provided.