Netflix / genie / 3205

94%

push

travis-ci-com

Fix exposing inconsistency in job status outside of persistence API

Within job launch logic there was a helper method which would query the job status and based on the returned value proceed with some logic to either update it or fall back to other logic. This works ok if all requests to the persistence service implementation go to a single cosistent backend. If, however, read only queries go to a read replica which may have lag or some other implementation entirely this breaks down without the service actually knowing why or how.

Moving the logic for this behind the persistence API and letting the launch service only act the returned job status from the source of truth api should fix this problem.

28 of 28 new or added lines in 2 files covered. (100.0%)

13453 of 14344 relevant lines covered (93.79%)

0.94 hits per line