1
96%
main: 96%

Ran 17 Dec 2025 08:14PM UTC

Files 6

Run time 0s

Badge

Embed ▾

Committed 17 Dec 2025 08:10PM UTC coverage: 96.216% (+0.2%) from 96.045%

Job # 20315941574.1

Build Type

Pull #332

github

Committed by

ghukill

Commit Message

Temporarily restore success and failure response properties

Why these changes are being introduced:

Until changes can be made to the StepFunction that would lean into a controlled
use of `next-step`, we need to keep `success` and `failure` as properties in the
response for early exits.  Primarily, this allows daily harvests with no records
to exit without error, which it is not.

How this addresses that need:
* Restores `success` and `failure` as allowed response properties
* Sets `result.success` and/or `result.failure` as needed for early exits
* Comments are applied indicating these are temporary measures

Side effects of this change:
* StepFunction will not error out for daily harvests that have zero records
* Once StepFunction is updated to utilize `next-step`, we'll want to fully
remove `success` and `failure` from the lambda response

Relevant ticket(s):
* https://mitlibraries.atlassian.net/browse/USE-279

Pull Request Pull Request #332: USE 279 - utilize and control next-step values

Run Details

356 of 370 relevant lines covered (96.22%)

0.96 hits per line

MITLibraries / timdex-pipeline-lambdas / 20315941574 / 1
96%
main: 96%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 20315941574.1

MITLibraries / timdex-pipeline-lambdas / 20315941574 / 1 96% main: 96%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 20315941574.1

MITLibraries / timdex-pipeline-lambdas / 20315941574 / 1
96%
main: 96%

README BADGES
x