-
Notifications
You must be signed in to change notification settings - Fork 171
[Feature Flags] Bind discovery results to the Agent endpoint #9352
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
leoromanovsky
wants to merge
1
commit into
master
Choose a base branch
from
leo.romanovsky/fflsdk-189-dotnet-discovery
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When the Agent endpoint changes after discovery has completed, clearing
_configurationonly prevents future subscribers from receiving the old snapshot; already-registered subscribers are not notified and continue using capabilities learned from the previous Agent. For example,RemoteConfigurationManager.SetRcmEnabledretains its prior value indefinitely if discovery against the replacement Agent fails, so clearing the cache does not actually enforce the endpoint boundary for normal production subscribers. Publish an invalidated snapshot or otherwise revoke the old capabilities when replacing the factory.Useful? React with 👍 / 👎.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Checked against base 0610b13b and head b16a7dcc. Existing subscribers retaining capability state is pre-existing; this PR fences cached replay and publication from obsolete endpoint generations. The RC example is narrower: exporter replacement creates a new RemoteConfigurationApi with no endpoint, and the probe confirmed zero requests before fresh discovery. A real SpanEventsManager does retain its old capability, so universal subscriber invalidation remains a separate policy/lifecycle follow-up. Leaving this open for that discussion rather than claiming it is fixed.