-
Notifications
You must be signed in to change notification settings - Fork 901
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix broken Functions CLI experience for projects with incomplete GCF 2nd Gen functions. #5684
Conversation
…ervice breaks the Functions CLI experience. The codebase assumes that "serviceConfig" property must be present in all 2nd Gen Functions in GCF. This isn't the case - 2nd Gen GCF functions may be missing a Cloud Run service if the build never succeeded.
Codecov ReportPatch coverage:
Additional details and impacted files@@ Coverage Diff @@
## master #5684 +/- ##
==========================================
- Coverage 55.71% 55.67% -0.04%
==========================================
Files 322 322
Lines 21836 21846 +10
Branches 4454 4461 +7
==========================================
- Hits 12166 12163 -3
- Misses 8602 8608 +6
- Partials 1068 1075 +7
... and 1 file with indirect coverage changes Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report in Codecov by Sentry. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
* type Bar = RequireKeys<Foo, "a" | "b"> | ||
* // Property "a" and "b" are now required. | ||
*/ | ||
export type RequireKeys<T extends object, Keys extends keyof T> = T & { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would you like me to make a DeepRequire like we have DeepOmit and DeepPick? Then you can say DeepRequire<Foo, "a.b" | "c">
…2nd Gen functions. (firebase#5684) The codebase assumes that "serviceConfig" property must be present in all 2nd Gen Functions in GCF. This is an incorrect assumption - 2nd Gen GCF functions may be missing a Cloud Run service if the build never succeeded. Also refactors `backend` module a bit to avoid calling out to Cloud Run to retrieve concurrency & cpu config - it's available on the GCF response now! Fixes firebase#4800
…2nd Gen functions. (#5684) The codebase assumes that "serviceConfig" property must be present in all 2nd Gen Functions in GCF. This is an incorrect assumption - 2nd Gen GCF functions may be missing a Cloud Run service if the build never succeeded. Also refactors `backend` module a bit to avoid calling out to Cloud Run to retrieve concurrency & cpu config - it's available on the GCF response now! Fixes #4800
The codebase assumes that "serviceConfig" property must be present in all 2nd Gen Functions in GCF. This is an incorrect assumption - 2nd Gen GCF functions may be missing a Cloud Run service if the build never succeeded.
Also refactors
backend
module a bit to avoid calling out to Cloud Run to retrieve concurrency & cpu config - it's available on the GCF response now!Fixes #4800