<retry> Solution for CRQ API limitation

[lendly-telus-com]

Description Risk Engine service account on ITSM CRQ API only allows one process at a time. Errors related to request timeouts could occur if multiple teams use the ITSM CRQ API simultaneously. Sam from ITSM also suggest a solution for the mean time which is retry

Acceptance Criteria Risk Engine service account should be promoted to admin account so that it would allow multiple process at a time. If the Risk Engine cannot be promoted to admin account. Retry function for API calls should be applied on TDRM and Risk Engine ITSM Plugin

Jeff: Retry function is already work in progress. Will apply to TDRM repo first after completing the function.

[lendly-telus-com]

Todo: handle diff https status

• explore possible error -

[lendly-telus-com]

retry mechanism is complete Critical: integration ITSM/TDRM repo

[lendly-telus-com]

itsm - effort tested 56 and got 10 failed

• invoking retry mechanism -- test WIP

[lendly-telus-com]

testing 100 -- ok no fail todo : implementation ITSM plugin

[lendly-telus-com]

tested by improvise todo: final implementation , . 90%

[lendly-telus-com]

code is complete merge

• todo > unit test
• challenge

[lendly-telus-com]

todo: integration test

[lendly-telus-com]

code review with Joseph

[lendly-telus-com]

affected by GKE migration

[lendly-telus-com]

local is fine - tested CRQ is fine Joseph - Vinh confirmation prior closing