feat: big query procedure for comparing validator versions #770
+120
−0
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.
Summary:
This PR introduces a new BigQuery function and updates the infrastructure to enable comparison of validation reports between two specified versions.
BigQuery Table Value Function
bigquery/compare-validation-reports.sql
: Added a new function,compare_validation_reports
, designed to compare validation reports between a previous and a current version. This procedure generates a merged report highlighting the differences in validation notices, including new and dropped notices.Terraform Configuration
infra/metrics/main.tf
: Updated Terraform configuration to include a new BigQuery routine resource,compare_validation_reports
. This change ensures the deployment and management of the new function in the infrastructure.Testing Instructions:
To test the function, execute the following call in the dev environment:
Example of connected sheet with the results
Please make sure these boxes are checked before submitting your pull request - thanks!
./scripts/api-tests.sh
to make sure you didn't break anything