Description

This PR implements the missing server-side template management functions in the Remote Config service to establish parity with the Firebase Remote Config REST API v1.

Previously, the Admin Node.js SDK treated the firebase-server namespace template as a read-only resource (accessible only via getServerTemplate() / initServerTemplate()). This PR adds public APIs for programmatic fetching, validation, publishing, rollback, and version history listing for the firebase-server template.

API Changes

Adds the following public methods to the RemoteConfig class:

• getServerConfigTemplate(): Promise<RemoteConfigTemplate>: Retrieves the current active version of the server-side Remote Config template.
• getServerConfigTemplateAtVersion(versionNumber: number | string): Promise<RemoteConfigTemplate>: Retrieves a specific version of the server-side Remote Config template.
• validateServerConfigTemplate(template: RemoteConfigTemplate): Promise<RemoteConfigTemplate>: Validates a server-side Remote Config template against the Remote Config backend.
• publishServerConfigTemplate(template: RemoteConfigTemplate, options?: { force: boolean }): Promise<RemoteConfigTemplate>: Publishes a server-side Remote Config template.
• rollbackServerConfigTemplate(versionNumber: number | string): Promise<RemoteConfigTemplate>: Rolls back the published server-side Remote Config template to a specific version.
• listServerConfigVersions(options?: ListVersionsOptions): Promise<ListVersionsResult>: Retrieves a list of published server-side Remote Config template versions.

These additions are mirrored in the generated API signature file etc/firebase-admin.remote-config.api.md.

Testing

• Extensively covered all new API client methods and service operations with new unit tests in:
  • test/unit/remote-config/remote-config-api-client.spec.ts
  • test/unit/remote-config/remote-config.spec.ts
• Ran the full test suite (npm run test:unit) ensuring all 6,235 tests pass.
• Verified that the linter (npm run lint) is completely clean.