Firebase CLI Deploy Failure: Missing Root Cause in Non‑Debug Output

Problem Statement

When a firebase deploy fails during the Functions phase, the CLI often reports only the function name and a brief error message. The underlying cause—such as a TypeScript compile error, missing dependency, or IAM permission issue—remains hidden unless the operator runs the command with --debug or consults Cloud Build logs.

Goal and Constraints

The goal is to reliably identify the root cause of a deployment failure without manually hunting through Cloud Build logs. Constraints include the fact that the default CLI output truncates detailed error information, and that the debug output may expose sensitive tokens if shared publicly.

Unresolved Behavior

It is unclear whether the Firebase CLI intentionally suppresses detailed error messages in non‑debug mode for brevity or due to a design decision, and if there is a configuration option to enable more verbose output without using --debug.

Specific Questions

• Does the Firebase CLI provide a flag (other than --debug) to include full Cloud Functions API error responses in the standard output?
• If not, how can operators programmatically retrieve the same detailed failure information without exposing sensitive data?
• Is there an official best‑practice workflow for diagnosing deploy failures that balances verbosity with security?