Extract Snapshots Collection

[DJensen94]

Add the snapshots collection and its query to the array of collections to extract

🗣 Description

Add the snapshots collection and its query to the array of collections to extract.

💭 Motivation and context

We need to pull the snapshots data so the Crossfeed application can recreate the VS report for stakeholders.

🧪 Testing

Tested query locally

✅ Pre-approval checklist

• This PR has an informative and human-readable title.
• Changes are limited to a single goal - eschew scope creep!
• All future TODOs are captured in issues, which are referenced
  in code comments.
• All relevant type-of-change labels have been added.
• I have read the CONTRIBUTING document.
• These code changes follow cisagov code standards.

✅ Pre-merge checklist

• Confirm that there are no issues/concerns from the AE side with deploying this change to Production.

✅ Post-merge checklist

• Dev team: Deploy this code to Production.

[dav3r]

Approved, though I have questions about what exactly this means, but I will talk with @climber-girl about them:

We need to pull the snapshots data so the Crossfeed application can recreate the VS report for stakeholders.

Do you only want snapshot data going forward (i.e. after this PR is merged and deployed) or do you also want the ~1.2 million snapshot documents that already exist in the CyHy DB? If the latter, then we will have to coordinate on that outside of this PR.

[DJensen94]

Approved, though I have questions about what exactly this means, but I will talk with @climber-girl about them:

We need to pull the snapshots data so the Crossfeed application can recreate the VS report for stakeholders.

Do you only want snapshot data going forward (i.e. after this PR is merged and deployed) or do you also want the ~1.2 million snapshot documents that already exist in the CyHy DB? If the latter, then we will have to coordinate on that outside of this PR.

We only want snapshots going forward.

[dav3r]

Do you only want snapshot data going forward (i.e. after this PR is merged and deployed) or do you also want the ~1.2 million snapshot documents that already exist in the CyHy DB? If the latter, then we will have to coordinate on that outside of this PR.

We only want snapshots going forward.

Excellent, thanks for confirming! 👍

[DJensen94]

@dav3r I am not authorized to merge, is there anything else that is required before this can be merged?

[dav3r]

@dav3r I am not authorized to merge, is there anything else that is required before this can be merged?

I think all that's left is for you to check any remaining checkboxes in the PR description that apply (e.g. the one about reading the CONTRIBUTING doc), then remove any checkboxes or sections (e.g. the Pre-merge checklist) that don't apply.

Note that I put a couple of post-merge tasks in, one for your team and one for my team.

[DJensen94]

@dav3r All checks complete, and we have reached out to AE so they are aware a new collection is on the way

[jsf9k]

Is the "All future TODOs are captured in issues, which are referenced in code comments." checkbox needed here or can that just be deleted? I didn't see any TODOs in this PR.

[dav3r]

@dav3r All checks complete, and we have reached out to AE so they are aware a new collection is on the way

@DJensen94 I just got an email from @jessiebeals stating:

Please do not deploy any changes if they will be automatically pushed to the AE with the daily extracts; we will need to coordinate with ME prior to pushing new data into their environment.

We are going to hold off on merging this PR until I get the green light from the AE side, mainly to ensure that this code is not unintentionally deployed before they are ready. I'm adding the blocked label to this PR for that purpose.