Bump Cloudquery to 5.19 and enable Sync Summary #1023
Conversation
|
This PR is stale because it has been open 30 days with no activity. Unless a comment is added or the “stale” label removed, this will be closed in 3 days |
|
This PR was closed because it has been stalled for 3 days with no activity. |
|
This PR is stale because it has been open 30 days with no activity. Unless a comment is added or the “stale” label removed, this will be closed in 3 days |
| @@ -3,7 +3,7 @@ import { Versions } from './versions'; | |||
|
|
|||
| export const Images = { | |||
| cloudquery: ContainerImage.fromRegistry( | |||
| `ghcr.io/guardian/service-catalogue/cloudquery:stable`, | |||
| `ghcr.io/guardian/service-catalogue/cloudquery:sha-2d6c95ee216c4fa9723aa3d0f8dc4e2a4636080b`, | |||
There was a problem hiding this comment.
Remnants from trying to test this branch in CODE, it can be reverted.
As is this PR doesn't currently work, in the original CloudQuery PR they suggest adding a send_sync_summary field to the destination plugin config but that doesn't seem to be correct
|
This PR is stale because it has been open 30 days with no activity. Unless a comment is added or the “stale” label removed, this will be closed in 3 days |
|
This PR was closed because it has been stalled for 3 days with no activity. |
What does this change?
Bumps Cloudquery to 5.19 and enable Sync Summary for all jobs.
Why?
Cloudquery 5.19 just released the ability to enable sync summaries. This feature sends a summary of the sync to the destination plugin in the form of a
cloudquery_sync_summarytable.We can possibly simplify our Cloudquery job by removing the initial postgres step. This also lets us generate a reliability report for our Cloudquery tasks.
How has it been verified?
Deployed to CODE.