This addresses the problem where we could not test gdrive access from a branch because the branch name was being used as the subfolder where the redacted data was stored on Google Drive. We needed to set the subfolder to always be main since that is where the released redacted data lives.
This should not be approved until the workflow for checking Google Drive access runs successfully. That workflow depends on the SERVICE_ACCOUNT_KEY_JSON secret and the GDRIVE_FOLDER variable being set right.
This addresses the problem where we could not test gdrive access from a branch because the branch name was being used as the subfolder where the redacted data was stored on Google Drive. We needed to set the subfolder to always be
main
since that is where the released redacted data lives.This should not be approved until the workflow for checking Google Drive access runs successfully. That workflow depends on the
SERVICE_ACCOUNT_KEY_JSON
secret and theGDRIVE_FOLDER
variable being set right.