Skip to content

Feat: on validation report, set service date range + backfill error handling#930

Merged
davidgamez merged 7 commits intomainfrom
feat/882-set-service-date-range
Mar 3, 2025
Merged

Feat: on validation report, set service date range + backfill error handling#930
davidgamez merged 7 commits intomainfrom
feat/882-set-service-date-range

Conversation

@Alessandro100
Copy link
Copy Markdown
Contributor

closes #882 and #881

Summary:

When the validation report is generated, add the service date range to the associated dataset. Also renamed the python function folder to better match the name of the function.

Added a error handling mechanism to the backfill function if getting the blog fails

Expected behavior:

When the validation report is processed, the associated dataset should have the service date range

If the blog exists, and it fails to get, it should default on the original url when backfilling the service date range

Please make sure these boxes are checked before submitting your pull request - thanks!

  • Run the unit tests with ./scripts/api-tests.sh to make sure you didn't break anything
  • Add or update any needed documentation to the repo
  • Format the title like "feat: [new feature short description]". Title must follow the Conventional Commit Specification(https://www.conventionalcommits.org/en/v1.0.0/).
  • Linked all relevant issues
  • Include screenshot(s) showing how this pull request works and fixes the issue(s)

@Alessandro100 Alessandro100 self-assigned this Mar 3, 2025
@Alessandro100 Alessandro100 force-pushed the feat/882-set-service-date-range branch from 930615b to cb7e274 Compare March 3, 2025 20:42
Copy link
Copy Markdown
Contributor

@cka-y cka-y left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[question]: I'm confused about the renaming of the files, is this not affecting the deployment of the function? I would expect a change in the terraform code after files are moved from one folder to another.

Copy link
Copy Markdown
Contributor

@cka-y cka-y Mar 3, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I suggested renaming the folder as it was confusing to map the function in GCP to the source code folder. But you're right lines 37-38 of the python functions terraform need to be updated

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Now I'm clear Thanks!

@emmambd emmambd linked an issue Mar 3, 2025 that may be closed by this pull request
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Now I'm clear Thanks!

Copy link
Copy Markdown
Member

@davidgamez davidgamez left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@davidgamez davidgamez merged commit 9bbee47 into main Mar 3, 2025
8 of 9 checks passed
@davidgamez davidgamez deleted the feat/882-set-service-date-range branch March 3, 2025 21:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Set service_date_range_start and service_date_range_end on validation report Backfill service_window_start and service_window_end data

3 participants