You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Reading through this: https://firebase.google.com/docs/remote-config/server it seems like server side remote config evaluations is something that could be supported.
Describe the solution you'd like
Allow remote config evaluation from a Java server.
Describe alternatives you've considered
LaunchDarkly
Additional context
Is there an ETA for this to be available?
The text was updated successfully, but these errors were encountered:
It would be highly beneficial to have the ability to fetch Firebase Remote Config parameters in real-time on the server-side using the Admin SDK.
Currently, the Admin SDK supports managing and publishing templates for Remote Config, but it doesn’t provide a way to dynamically retrieve these configurations, like the client SDK does (e.g., with fetchAndActivate() for mobile/web). In many server-side use cases (like microservices), it’s important to adapt behavior based on the latest configuration, similar to how front-end applications adjust UI and functionality dynamically.
Having this feature in the Admin SDK would allow developers to access and act on dynamic configuration values from the server, improving flexibility and reducing the need for custom REST API wrappers around Firebase's Remote Config.
I believe this would align the SDK's capabilities across environments and would be a very welcomed addition.
Is your feature request related to a problem? Please describe.
Reading through this: https://firebase.google.com/docs/remote-config/server it seems like server side remote config evaluations is something that could be supported.
Describe the solution you'd like
Allow remote config evaluation from a Java server.
Describe alternatives you've considered
LaunchDarkly
Additional context
Is there an ETA for this to be available?
The text was updated successfully, but these errors were encountered: