Allow us to pass a factory of FirebaseAppConfig to AngularFireModule.initializeApp()

It would be great if we get an option to pass a factory function of FirebaseAppConfig to AngularFireModule.initializeApp(). In some cases such as using a webpack to get enviroment variables and AOT compiler it is impossible now to initialize AngularFireModule with correct config parameters. This is because of webpack does not run yet at the moment of module compilation. The ability to pass a factory of FirebaseAppConfig to static initialization function would be a solution for this and maybe other similar problems. One related issue already exists: https://github.com/angular/angularfire2/issues/1281

[brendonwm]

Does anyone have an example of how to “pass a factory of FirebaseAppConfig to AngularFireModule.initializeApp()” or alternative solution using runtime DI? Thanks.

[juristr]

Thinking of this, it would also be cool if we could get rid of the compile-time configuration and get the Firebase config at runtime, like via some call to a config JSON (I recently wrote an article on that).

The point is when I’m creating a CD pipeline I’d like to build once and then move that same package from testing, staging to production environment, without the need of rebuilding my Angular app again. That obviously doesn’t work when you use the Angular CLI environment.<env>.ts approach. Rather, I’d like to fetch it via a config using an approach like Angular’s APP_INITIALIZER.