Add logging to data pipeline#254
Open
vipinsamreddy wants to merge 4 commits into
Open
Conversation
Code Coverage Report: Only Changed Files listed
Minimum allowed coverage is |
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
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.
Description
created a dedicated pipeline report directory under RUNNER_TEMP
kept per-stage JSON summaries for source versioning, input download, SQL generation, maintenance enable/restore, ETL, review-seed
backup, environment backup, and review restore
preserved ETL and pg_dump logs into the report artifact, instead of only leaving them in working files
recorded retry metadata explicitly for ETL: attempts, retry count, retry classification
made skipped paths explicit for backup and restore stages
added a final markdown run summary to GITHUB_STEP_SUMMARY showing each stage’s status, retries, and concise summary
uploaded the whole structured report as one artifact: data-pipeline-stage-report-
-also fixed the maintenance-restore summary so it no longer depends on the brittle inline || expression.
Related Trello Ticket
Provide the link to the trello card here.
Type of change
Please delete options that are not relevant.
How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration
Checklist
Screenshots (if applicable)
Add UI changes, logs, console outputs anything to help reviewers.