GLOWS: reprocess L3b+ on new L3a (Phase D deferred)

[jtniehof]

Summary

The GLOWS L3b initializer is designed to to make updated L3b and later based on updates to GLOWS L3a.

Perform an integration test of this functionality.

Requirements

• All of these requirements are performed by the daily run of the initalizer.
• For new L3a files, process L3b and L3c for the CR that includes that L3a, and then process new L3d
• Gather all updated L3a so that this isn't thrashing
• Use the latest external inputs when processing, i.e. if L3a updates, update L3a AND external inputs
• No need to check / reprocess if only external inputs have been updated

Related tickets

#43, #44

Estimate

4 hours for a potential integration test

[jtniehof]

GlowsL3BCInitializer does this work (look at should_process_cr_candidate).

The daily check looks at all CRs for either new or updated L3a, and will reprocess as necessary. Since this is a poll, not a trigger, there is no thrashing.

This line will request a new L3b if the set of L3a files passed in is different from the set of files used to make the L3b. So the initializer will proceed for new /updated L3a.

[jtniehof]

The requirement to use updated external dependencies is met because those are downloaded fresh before even checking for any updated files -- the initializer does not try to reuse old external deps.

The processing of L3b, L3c, and L3d is met because "reprocessing" is the same code path as initial processing.

And there is no reprocessing on external inputs because the code performs no checking of their versioning, only if they are available when we have new L3a to process.