Doc enhancement: example of CLI installation of `firestore-bigquery-export` using --paramsFile

Extension: firestore-bigquery-export

This feature request is for extension: docs enhancement

What feature would you like to see?

Documentation for how to install this extension via the CLI non-interactively. Running firebase ext:install firestore-bigquery-export --project=t8s-project requires interactivity in answering the various questions. The usage string indicates that --params <paramsFile> is how one would go about providing param variable values, but there is no further description or example as to what those parameters could (or must) be.

How would you use it?

Reduce time and - more importantly - errors in setting up new Firebase projects.

[gregfenton]

FOR FUTURE ME: I just submitted another feature request to Firebase Support: allow setting of an extension’s instanceId as a parameter from --param <paramsFile>. Currently on lines 77-92 of firebase-tools/src/commands/ext-install.js, if the default instanceId is already in use then it prompts the user for a new ID. I would like to be able to specify the ID entirely from the command-line and not allow any “defaults” to get in the way.

[jhuleatt]

Thanks for the feedback! The --params flag is documented in the Firebase docs, although it is a bit hidden:

I’m adding in our tech writer @kevinthecheung regarding the feedback that we should update the docs to note that the install command is never truly non-interactive.

Regarding the enhancements, @gregfenton can you please file those as a feature request on the firebase-tools repository? They sound like good ideas worth considering, and all of our install CLI code lives in the firebase-tools repo.