You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We current deploy all of our cloud functions in one batch. Google recommends we deploy functions in batches no larger than 10 to avoid hitting the function deploy rate limit (iirc it's 80 functions within 100 seconds for V1 and 60 functions over 60 seconds for V2). We currently have 44 functions and that number will only increase - we should start thinking about how to segment our function deploys into chunks of 10 or fewer functions to avoid hitting this and ending up in an undesirable partial deployment state.
Success Criteria
Back-end function deploys are segmented into batches of 10 or fewer functions
Problem
We current deploy all of our cloud functions in one batch. Google recommends we deploy functions in batches no larger than 10 to avoid hitting the function deploy rate limit (iirc it's 80 functions within 100 seconds for V1 and 60 functions over 60 seconds for V2). We currently have 44 functions and that number will only increase - we should start thinking about how to segment our function deploys into chunks of 10 or fewer functions to avoid hitting this and ending up in an undesirable partial deployment state.
Success Criteria
Related Links
The text was updated successfully, but these errors were encountered: