Repository navigation
Refactor cloud integration flows - #182
Merged
Merged
Conversation
… fix timestamp missing utc
…een generated, fix regression bug on creating stratum 7 during refactoring
Member
Author
|
@LOCEANlloydizard: I'm self-merging this to keep the codebase up to date. You may have to resolve conflicts in |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR refactors the cloud integration flows to use the new repo structure by splitting functions into
flows,tasks,opertaions, andutils.Note this PR also reverted changed made in #179 (which was to use database ledger for the real-time raw2Sv flow) -- it was only a partial migration and all downstream flows still use CSV files, which is messy. I think it's better to just do the database ledger update for all flows at once. @LOCEANlloydizard and I agreed on not touching the CPS flows though, which currently uses the raw2Sv database ledger.