Skip to content

test(ffe): validate Go agentless EVP egress - #7589

Draft
leoromanovsky wants to merge 3 commits into
pavlo.khrebto/FFL-2695/go-agentless-configurationfrom
leo.romanovsky/ffe-agentless-evp-fallback-go-tests
Draft

test(ffe): validate Go agentless EVP egress#7589
leoromanovsky wants to merge 3 commits into
pavlo.khrebto/FFL-2695/go-agentless-configurationfrom
leo.romanovsky/ffe-agentless-evp-fallback-go-tests

Conversation

@leoromanovsky

@leoromanovsky leoromanovsky commented Aug 26, 2026

Copy link
Copy Markdown
Contributor

Motivation

FFL-1491

Go needs system-test coverage proving exposure and flagevaluation delivery through Agent, direct, and serverless-sidecar EVP routes.

Changes

  • Add the shared flagevaluation egress contract for Agent, direct, and serverless-sidecar scenarios.
  • Enable Go agentless exposure and flagevaluation route coverage in the manifest.
  • Assert direct intake host, response status, API-key authentication, and absence from the unused route.
  • Keep buffered writers alive through flush and isolate aggregate counts by targeting key.
  • Trust the checked-in MITM CA in the Go test image while retaining TLS verification.

Decisions

  • Validate exposure and flagevaluation together in each deployment topology.
  • Accept the API key as either its expected value or the capture layer's redacted value.
  • Preserve exact payload, aggregate-count, deduplication, and route-exclusion assertions.
  • Keep this draft stacked on pavlo.khrebto/FFL-2695/go-agentless-configuration.

Validation

  • ./format.sh
  • ./build.sh golang -w net-http using the local Go EVP branch artifact
  • FEATURE_FLAGGING_AND_EXPERIMENTATION: 2 passed
  • FEATURE_FLAGGING_AND_EXPERIMENTATION_AGENTLESS_DIRECT: 2 passed
  • FEATURE_FLAGGING_AND_EXPERIMENTATION_AGENTLESS_SERVERLESS: 2 passed

Activate Go direct and serverless exposure and flagevaluation contracts, keep buffered writers alive through capture, and trust the checked-in fixture CA for intercepted test TLS.

Environment: Datadog workspace
@github-actions

Copy link
Copy Markdown
Contributor

CODEOWNERS have been resolved as:

manifests/golang.yml                                                    @DataDog/dd-trace-go-guild
tests/ffe/test_exposure_egress.py                                       @DataDog/feature-flagging-and-experimentation-sdk @DataDog/system-tests-core
tests/ffe/test_flag_eval_evp.py                                         @DataDog/feature-flagging-and-experimentation-sdk @DataDog/system-tests-core
tests/test_the_test/scenarios.json                                      @DataDog/system-tests-core
utils/build/docker/golang/net-http.Dockerfile                           @DataDog/dd-trace-go-guild @DataDog/system-tests-core

@datadog-datadog-prod-us1-2

datadog-datadog-prod-us1-2 Bot commented Aug 26, 2026

Copy link
Copy Markdown

Tests

🎉 All green!

❄️ No new flaky tests detected

🔄 Datadog auto-retried 80 jobs - 1 passed on retry View in Datadog

This comment will be updated automatically if new data arrives.
🔗 Commit SHA: 7fc99ad | Docs | View more details | Give us feedback!

leoromanovsky and others added 2 commits August 26, 2026 15:51
Keep the Go direct-intake egress contract focused on routes and API-key authentication; fingerprint coverage ships independently.

Environment: Datadog workspace
Filter the shared egress contract by its targeting key so exposure and flagevaluation setup traffic cannot inflate one another.

Environment: Datadog workspace

Co-Authored-By: Claude GPT-5 <noreply@anthropic.com>
@linear-code

linear-code Bot commented Aug 26, 2026

Copy link
Copy Markdown

FFL-1491

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant