ЕСОЗ - публічна документація

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »


Specification

GraphQL

Purpose

This WS is designed to assign pair of master_person_id and person_id to a reviewer.

Statements 

  1. One assignee can have only one merge_request in status 'NEW'
  2. One assignee can't have more than max_postponed_value marge_requests in status 'POSTPONED'
  3. If assignee reach postponed_requests_limit, new merge_request can't be assigned to him
  4. Assignee can't assign same merge_request more than once
  5. Assignee can postpone merge request
  6. Until assignee won't make final decision, assignee can't be change for merge_request

Authorize

    1. Verify the validity of access token
      1. in case of error return 401 ('Access denied')
    2. Check user scope merge_candidate:assign in order to perform this action
      1. in case of error generate 401 response ('Invalid scopes')

Verify role

Extract from token:

  1. Validate client_id (is_blocked=false)
    1. in case of error return 403 Error ('Client is blocked')
  2. Check user_roles by client_id 
    1. check whether exist role NHS_REVIEWER 
      1. in case of error return 403 Error ('User doesn't have required role')

Identify User 

Knowing token and client find user_id from mithril.users

Fetch manual_merge_candidate

From table manual_merge_candidate find:

  1. Record in status = 'NEW'
  2. Assignee_id=null
  1. Priority by records which already has some decisions 
    1. join table  manual_merge_requests on manual_merge_requests.merge_candidate_id=manual_merge_candidates.merge_candidate_id and manual_merge_requests.assignee_id<>$user_id
    2. choose manual_merge_requests.merge_candidate_id  order by  count() DESC
  2. manual_merge_candidate must satisfy constraint: merge_candidate_id+assignee_id in table manual_merge_requests


Validate request

  1. Check whether this user doesn't have other merge_requests in status='NEW'
    1. check manual_merge_requests by assignee_id=$user_id and status='NEW'
      1. in case of error return conflict error 'CONFLICT' - 'Assignee is not allowed to ask for new merge request'
  2. Check amount of postponed merge_requests for current employee_id
    1. check qty from manual_merge_requests by assignee_id=$user_id and status='POSTPONED'
      1. in case of qty<postponed_requests_limit return conflict error 'CONFLICT' - 'Assignee reached limit in postponed merge_requests'
  3. Check there is no record for merge_candidate_id+assignee_id 
    1. in table manual_merge_requests fetch a record by condition merge_candidate_id+$user_id
      1. in case of such record exists return conflict error 'CONFLICT' - 'Assignee can review merge_request only once'
  4. Check whether merge_candidate_id can be reviewed
    1. verify merge_candidate_id has status NEW and assignee_id is null in table manual_merge_candidates
      1. in case of error return conflict error 'CONFLICT' - 'Invalid merge_request to be reviewed'
  5. In case there is no merge candidate in status NEW which wasn't verified by $user_id return 404 Error
    1. 'No merge request is found'


Update assignee for merge_candidate

  1. Update assignee_id in manual_merge_candidates  to $user_id
  2. Update updated_at = now()
  3. Update updated_at = $user_id

manual_merge_candidates

Field Value
assignee_id$user_id
updated_atnow()

Make merge_request for assignee

Insert into table manual_merge_requests a record

column
value
idUUID
merge_candidate_id$merge_candidate_id
assignee_id$user_id
inserted_atnow()
updated_atnow()
statusNEW
commentnull

Add a record to audit log

After status was changed  add new record to audit_log

field
value
idgenerate UUID
actor_id$user_id
resource'manual_merge_process'
resource_id$manual_merge_process.id
changeset{status:NEW}
inserted_atDATETIME
  • No labels