Firebase Cloud Functions gen2 deployment failure: CLI debug vs Cloud Build logs

When a Firebase Cloud Functions (gen2) deployment fails, the goal is to locate the root‑cause information as quickly as possible while respecting the access boundaries of the team member performing the triage. The Firebase CLI can be run in verbose mode to show detailed API responses, but the summary it prints often hides the underlying Cloud Build error, and the log URL may be omitted or truncated. Conversely, the definitive build logs reside in Cloud Build within the linked Google Cloud project, which requires permissions that collaborators who only have Firebase console roles may not possess.

This creates a decision point: should the investigator first rely on the verbose CLI output to surface the failure details, or proceed directly to Cloud Build logs despite the potential permission hurdle? The answer influences both the speed of diagnosis and the need to adjust IAM roles or workflow tooling.

• Does the verbose CLI output reliably contain the Cloud Build log link or the full error message for a failed gen2 Functions deploy?
• If the CLI output lacks the necessary detail, what minimal Google Cloud IAM permissions are required to view the relevant Cloud Build logs without granting broader project access?
• Can the Firebase CLI be configured or invoked in a way that automatically surfaces the Cloud Build log URL in its output, reducing the need to switch consoles?