feature/script-for-retroactive-session-content-hashing

[isaacna]

Link to Relevant Issue

This pull request resolves #158

Description of Changes

Added a script for adding the content hash for every session in a firestore instance.

Running this script would be:

add_content_hash_to_sessions --google_credentials_file {PATH_TO_CREDS_FILE}

Testing

Ran this on my personal firestore instance and tested the following:

• All session content hashes are added
• We properly log which sessions still don't have the content hashes

[codecov]

Codecov Report

Merging #159 (8b5cf08) into main (ef049ad) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #159   +/-   ##
=======================================
  Coverage   94.54%   94.54%           
=======================================
  Files          50       50           
  Lines        2548     2548           
=======================================
  Hits         2409     2409           
  Misses        139      139           

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update ef049ad...8b5cf08. Read the comment docs.

[evamaxfield]

I think this makes sense for the most part! I will try to come up with a deployment strategy for implementing in cookiecutter. I kind of want to make a GitHub action that runs this and any future changes we need to make.

"Action: Upgrade 3.0.3 - 3.0.4 -- click to run" if that makes sense?

[isaacna]

I kind of want to make a GitHub action that runs this and any future changes we need to make.

"Action: Upgrade 3.0.3 - 3.0.4 -- click to run" if that makes sense?

I'm good with this. Not sure actions supports this, but we could try to make this action appear conditionally on if the version is <= 3.0.3