re-enabled cancel or terminate lock info pids via masu #4443

cgoodfred · 2023-06-09T13:52:47Z

Jira Ticket

Description

This change will enable the functionality to cancel/terminate PIDs via the masu db performance endpoints.

Testing

Checkout Branch
Create a source or two, doesn't need data, just to exist so make create-test-customer is fine.
Visit the lock-info db-performance page and verify there are no locks: http://localhost:5042/api/cost-management/v1/db-performance/lock-info/
Open a PSQL window to run a little SQL in and run the following:

BEGIN;
UPDATE public.api_provider SET paused = false;

Go to the sources endpoint (http://localhost:8000/api/cost-management/v1/sources/) and decide on a source to try and delete, trigger a delete on that source.
Go back to the lock-info page and see information on a deadlock showing.
Cancel the PID for the source delete using the provided button after clicking through the verification prompts.
The page should refresh and the block should be cleared. The source delete page will now show information about being cancelled due to user request:

"Source removal resulted in UNKNOWN error: OperationalError: canceling statement due to user request\nCONTEXT:  while deleting tuple (0,6) in relation \"api_provider\"\n"

Notes

...

codecov · 2023-06-09T14:11:56Z

Codecov Report

Merging #4443 (510afd6) into main (eb10a9a) will decrease coverage by 0.1%.
Report is 271 commits behind head on main.
The diff coverage is 33.3%.

Additional details and impacted files

@@           Coverage Diff           @@
##            main   #4443     +/-   ##
=======================================
- Coverage   95.9%   95.8%   -0.1%     
=======================================
  Files        699     699             
  Lines      71884   71950     +66     
  Branches    5778    5787      +9     
=======================================
+ Hits       68905   68924     +19     
- Misses      1996    2038     +42     
- Partials     983     988      +5