-
-
Notifications
You must be signed in to change notification settings - Fork 158
Add Support for Cloud Run Jobs #1965
Copy link
Copy link
Open
Labels
CI/CDGitHub Actions, deployments, or build pipeline stuffGitHub Actions, deployments, or build pipeline stuffReady for DevelopmentAutomatically assigned to issues that are ready to be picked upAutomatically assigned to issues that are ready to be picked upbackendBackend DevelopmentBackend DevelopmentenhancementNew feature or requestNew feature or request
Metadata
Metadata
Assignees
Labels
CI/CDGitHub Actions, deployments, or build pipeline stuffGitHub Actions, deployments, or build pipeline stuffReady for DevelopmentAutomatically assigned to issues that are ready to be picked upAutomatically assigned to issues that are ready to be picked upbackendBackend DevelopmentBackend DevelopmentenhancementNew feature or requestNew feature or request
Problem
When we run one-off scripts, we currently have to do it against a dev's local machine. This leads to a number of recurring, preventable issues - ranging from auth differences between local dev and deployed instances to resource issues with personal machines to simple environment inconsistency. There is also no permanent record of a job's results after it's been run, making it difficult to track the state of various backfills.
To make these tasks more robust, we should move from running these scripts locally to running them in a Google Cloud Run environment - this will let us run one-off scripts with a similar architecture to our existing Firebase Functions.
Success Criteria
scriptsfolder:Additional Notes