feat(ffe): add configuration resolution and agentless endpoints - #4195
Draft
pavlokhrebto wants to merge 1 commit into
Draft
pavlokhrebto wants to merge 1 commit into
pavlokhrebto wants to merge 1 commit into
Conversation
|
8 tasks
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
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.
Description
This is the first change in the stacked implementation of agentless Feature Flag Evaluation delivery.
It:
DD_SITE, and the initialization timeoutDD_EXPERIMENTAL_FLAGGING_PROVIDER_ENABLEDas deprecatedScope of this PR
This PR adds configuration and endpoint foundations only. It does not start polling, wire source selection into tracer startup, or change evaluation behavior yet. Those pieces follow in subsequent PRs in the stack, so this PR should not be merged independently from the completed stack.
The currently supported OpenFeature PHP SDK does not expose provider initialization, shutdown, status, or event APIs. This does not affect this foundational PR, but later integration will use the documented first-evaluation compatibility path until upstream lifecycle support exists.
Validation
cargo fmt --package datadog-php -- --check./tooling/generate-supported-configurations.shgit diff --checkcargo check --locked --libcargo clippy --locked --lib -- -D warningscargo test --locked --lib ffe::settingsmake -j8Reviewer checklist
Relates to FFL-2705.