Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
fix: Read secrets from new collection (#98)
Pairing Bot holds many secrets, and some of them are config values! Right now, those config secrets are stored in single-document collections that (in my experience) have names that don't clearly map to their usage. This starts reading them all out of a new collection named "secrets", and each document contains a single secret token. I've already copied the secrets to their new locations, which can be verified in the Google Cloud console for both environments. (The RC API access token won't match, though, because I generated a new one out of my RC account.) After both the dev and prod bots deploy successfully, I'll delete the old unused secret collections.
- Loading branch information