Export summer workshops to gdrive

[megcrenshaw]

Updates the existing export file to use a new gsheet. I followed the process detailed in #39120, which references #32597.

• jira ticket: PLAT-1287 (See the sheets link there)

Testing story

Tested end-to-end locally with development secrets configured in Secret Manager. I added the configuration needed in development.yml.erb in #43476 for local testing––to overwrite values in the Secrets Manager, put in locals.yml.

Things to check:

• The Secrets Manager has the correct applications_2022_2023_gsheet_key for the file in different environments. Should be in all environments to avoid errors. The key in the development environment is different for testing.
• The cdo-gdrive-export-prod account has write access to the file. Note that if you're testing locally, you need the staging equivalent account for write access to the file, unless you have prod credentials set up in your locals.yml file.

If you are wanting to put credentials into your locals.yml file, it should look something like

gdrive_export_secret:
  type: "service_account"
  project_id: ""
  private_key_id: ""
  private_key: "-----BEGIN PRIVATE KEY-----\n       \n-----END PRIVATE KEY-----\n"
  client_email: ""
  client_id: ""
  auth_uri: ""
  token_uri: ""
  auth_provider_x509_cert_url: ""
  client_x509_cert_url: ""

Let me know if you're wanting to test locally and running into trouble.

Deployment strategy

Follow-up work

Privacy

Security

All secrets are in the AWS Secrets Manager.

Caching

PR Checklist:

• Tests provide adequate coverage
• Privacy and Security impacts have been assessed
• Code is well-commented
• New features are translatable or updates will not break translations
• Relevant documentation has been added or updated
• User impact is well-understood and desirable
• Pull Request is labeled appropriately
• Follow-up work items (including potential tech debt) are tracked and linked

[tim-dot-org]

thanks for making this much more readable!