Repository navigation
test(ffe): validate Ruby agentless EVP delivery and fallback - #8189
Draft
leoromanovsky wants to merge 1 commit into
Draft
leoromanovsky wants to merge 1 commit into
leoromanovsky wants to merge 1 commit into
Conversation
Contributor
|
|
❌ ErrorsYour PR has failed checks. Please review the issues below and take necessary action before merging. 🚦 2 Pipeline jobs failed
ℹ️ InfoNo other issues found (see more)🧪 All tests passed Useful? React with 👍 / 👎 This comment will be updated automatically if new data arrives.🔗 Commit SHA: 0a2c969 | Docs | View more details | Give us feedback! |
This branch has not been deployed
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.
Motivation
Ruby's agentless configuration can now deliver exposures and flag evaluations without a compatible local receiver, but system coverage must catch duplicate delivery and credential leakage when a route fails. This implements FFLSDK-196 alongside dd-trace-rb #6574.
Changes
Enable both Ruby signals through a full Agent, serverless-init and direct HTTPS mock intake. Eight fault scenarios target each writer with 404, 405, 403 or connection loss after the receiver reads the complete body: 404/405 replay the same payload once, while 403 and ambiguous failures move only future batches. Assertions cover shared routing, identity headers, credential isolation, evaluation values and duplicate delivery.
The Rails 7.2 shutdown scenario runs Puma as PID 1 and records server closure before the SDK's existing exit flush, allowing the existing strict shutdown contract to run for Ruby. Other SDKs remain gated until their new scenarios are validated.
Validation: 16 selected contracts pass on the gem built from Ruby
ff41edc95fd4ea4fa59bd4793a6bfe5c76d923e1: full Agent 7.84.5 (1), serverless-init 1.10.4 (2), direct including shutdown (3), historical RC/Agent (2), and fault cases (8)../format.shpasses. Gem SHA-256:f851442d689cf158ee481dac8a67fcf6daa2f7c9083f17d3f7c3dd28ca5cb3b0.These runs use local containers and mock intake; they do not establish production acceptance. Activation depends on the Ruby implementation above; ordinary CI using another Ruby artifact is separate evidence.
Workflow
system-tests-reviewers: ask to one of youre co-worker familiar with the tested feature.system-tests-core(slack)🚀 Once your PR is reviewed and the CI green, you can merge it!
🛟 #apm-shared-testing 🛟