request: Configurable firebase.json output directory ("--firebase-out=<PATH>")

[kNoAPP]

Is there an existing feature request for this?

• I have searched the existing issues.

Command

flutterfire configure --yes --project=<FIREBASE_PROJECT_ID> --firebase-out=<PATH>

Description

As a developer, I want to be able to dictate where the firebase.json generated file is written to.

Reasoning

This feature is useful for compatibility with projects with abnormal file structures, multi-environments, or special CI/CD instructions.

Additional context and comments

The other generated outputs have path-supported flags:

flutterfire configure \ 
--yes \
--project=your-project-id \
--platforms=ios,macos,android,web \
**--android-out=android/app/src/release/google-services.json \**
--android-package-name=com.example.myapp.release \
--ios-build-config=Release \
**--ios-out=/ios/release/GoogleService-Info.plist \**
--ios-bundle-id=com.example.myApp.ios.release \
--macos-build-config=Release \
**--macos-out=/macos/release/GoogleService-Info.plist \**
--macos-bundle-id=com.example.myApp.macos.release \
--web-app-id=<1:XXX:web:XXX> \
**--out=lib/release/firebase_options.dart**

Supporting the firebase.json location would further future-proof the CLI.

[github-actions]

Hello 👋, to help manage issues we automatically close stale issues.

This issue has been automatically marked as stale because it has not had activity for quite some time.Has this issue been fixed, or does it still require attention?

This issue will be closed in 15 days if no further activity occurs.

Thank you for your contributions.

[akurnaz]

@kNoAPP Could you find any solution?

[kNoAPP]

@kNoAPP Could you find any solution?

Denial, pain, bargaining, reflection, reconstruction, acceptance.

In all seriousness, I do hope the flutterfire team reconsiders this feature because it would be nice to have. I've had to write some custom scripts to work around it.