Skip to content

Conversation

@brittanycho
Copy link
Contributor

Cloud Run No Build Initial MVP Implementation v2

@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @brittanycho, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request delivers the foundational components for 'no-build' deployments to Cloud Run, primarily focusing on enabling Dart 3 functions. It allows developers to specify Cloud Run service configurations directly through a functions.yaml file, providing granular control over the container image and execution commands. The changes involve significant updates to the deployment pipeline, including how function definitions are parsed, source code is packaged, and Cloud Run services are managed via the V2 API, paving the way for more flexible serverless deployments.

Highlights

  • Cloud Run No-Build Support: Introduced initial MVP implementation for 'no-build' deployments to Cloud Run, allowing users to define services via a functions.yaml file with custom base images, commands, and arguments.
  • Dart 3 Runtime Integration: Added support for Dart 3 as an experimental runtime, enabling 'no-build' functions to be deployed using Dart.
  • Cloud Run V2 API Integration: The deployment fabricator now uses the Cloud Run V2 API for creating, updating, and deleting Cloud Run services, replacing previous placeholder errors.
  • Source Packaging Enhancements: Modified source packaging to support tar.gz archives for 'no-build' Cloud Run deployments, alongside the existing zip format for other function types.
  • Backend and IAM Updates: Updated backend definitions to include new fields for Cloud Run (e.g., baseImageUri, command, args) and adjusted IAM checks to exclude 'run' platform functions from standard HTTP IAM verification.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request introduces support for a "no build" deployment to Cloud Run for Firebase Functions, a significant new feature. The changes are extensive, touching deployment logic, configuration parsing, and adding a new runtime delegate for Dart. The implementation correctly adds a new "run" platform, handles tar.gz packaging for the source, and uses the Cloud Run v2 API for deployment. The addition of manual verification files and new tests is a good practice.

I have a couple of suggestions for improving code quality:

  1. There are several instances of empty JSDoc comments being added. These should be removed or filled with meaningful content.
  2. The new nobuild runtime delegate uses several as any type assertions that are no longer necessary due to updated type definitions. Removing them will improve type safety.

Overall, this is a solid MVP implementation.

@brittanycho brittanycho requested a review from taeold January 7, 2026 21:50
},
client: "cli-firebase",
labels: { ...endpoint.labels, "goog-managed-by": "firebase-functions" },
annotations: {},
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I see few missing configs like

  • timeout
  • serviceAccount
  • labels for triggers, like callable function, scheduled function, etc
  • env vars

Fix or leave a todo?

}
const configForUpload = shouldUseRuntimeConfig(localCfg) ? runtimeConfig : undefined;
const exportType = backend.someEndpoint(wantBackend, (e) => e.platform === "run")
? "tar.gz"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit* I think zip deploy may add support for .zip soonish?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I see, do you think above would be best to add as a todo once they add the support or preemptively add it now?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants