HC-247: Add User Access Control to Mozart API endpoints #25
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Added access control to Mozart API for
/job/submit
and/job/list
. This update is forv4.0
.Updated behavior:
/job/submit
-username
will now be added to the job metadata. We had this only when jobs were submitted from Tosca but the API. Now we propagate username information to the job's metadata and they show up under the username facet on Figaro./job/list
-If
username
is not provided, get all jobs information.If
username
provided, filter to only jobs for that user.detailed
for specifying the format of response.If
detailed
isTrue
then, returns job ID, job status, job type and job param values. I extended the amount of information returned here because having hundreds of Job Ids are not useful to users when they are looking for their job history. It's more informative when they can see what those jobs were.If
detailed
isFalse
then, it defaults to previous behavior of returning list of job IDs.Made this backwards compatible, so even if detailed flag is not provided the behavior will be same as before.