💥 Remove remoteConfigurationId from RUM SDK (breaking change, v7)#4244
Draft
mormubis wants to merge 1 commit intoadlrb/ssi-e2efrom
Draft
💥 Remove remoteConfigurationId from RUM SDK (breaking change, v7)#4244mormubis wants to merge 1 commit intoadlrb/ssi-e2efrom
mormubis wants to merge 1 commit intoadlrb/ssi-e2efrom
Conversation
BREAKING CHANGE: remoteConfigurationId and remoteConfigurationProxy are
removed from datadogRum.init() options.
Migration guide:
// Before (v6)
datadogRum.init({ remoteConfigurationId: 'xxx', ...options })
// After (v7)
import { fetchRemoteConfiguration } from '@datadog/browser-remote-config'
const result = await fetchRemoteConfiguration({ applicationId, configId, site })
if (result.ok) {
datadogRum.init({ ...result.value.rum })
}
The remote configuration logic now lives in @datadog/browser-remote-config,
giving customers more control: parallel fetching, custom caching, error handling.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Motivation
As part of the SSI (Single-Step Instrumentation) Phase 6 initiative, the
remoteConfigurationIdfield and the entire remote-configuration integration that was previously embedded inrum-coreis being removed. Remote configuration is now handled by the standalone@datadog/browser-remote-configpackage (PR2) consumed by the new@datadog/browser-sdk-endpointpackage (PR3), which acts as the SSI entry point.This is a v7 breaking change: any customer who configured
remoteConfigurationIdmust migrate to the new endpoint-based approach.Changes
remoteConfigurationIdfromRumInitConfigurationand all runtime code inrum-corepackages/rum-core/src/domain/configuration/remoteConfiguration.tsand its specspackages/rum-core/src/domain/configuration/jsonPathParser.spec.ts(moved to@datadog/browser-remote-config)preStartRum.ts,configuration.ts,eventTracker.ts, and their index exports to remove all references to remote configurationTest instructions
Checklist