Skip to content

Conversation

@ygree
Copy link
Contributor

@ygree ygree commented Feb 12, 2024

Motivation

The backend normalizes service and env values, so we need a test case that verifies such a scenario to make sure that a Tracer is case-insensitive of env or service name values.

Changes

Add sevice+env case-insensitivity test.
Extract service+env test to TestDynamicConfigV1_ServiceTargets.
Enable TestDynamicConfigV1_ServiceTargets for the Java Tracer v1.30+.

Workflow

  1. ⚠️ Create your PR as draft ⚠️
  2. Work on you PR until the CI passes (if something not related to your task is failing, you can ignore it)
  3. Mark it as ready for review
    • Test logic is modified? -> Get a review from RFC owner. We're working on refining the codeowners file quickly.
    • Framework is modified, or non obvious usage of it -> get a review from R&P team

🚀 Once your PR is reviewed, you can merge it!

🛟 #apm-shared-testing 🛟

Reviewer checklist

  • Relevant label (run-parametric-scenario, run-profiling-scenario...) are presents
  • No system-tests internal is modified. Otherwise, I have the approval from R&P team
  • CI is green, or failing jobs are not related to this change (and you are 100% sure about this statement)
  • A docker base image is modified?
    • the relevant build-XXX-image label is present
    • To R&P team: locally build and push the image to hub.docker.com
  • A scenario is added (or removed)?
    • Get a review from R&P team
    • Once merged, add (or remove) it in system-test-dasboard nightly

@ygree ygree force-pushed the ygree/remote-config-svc-env-check branch 4 times, most recently from 6c19161 to 2bf181b Compare February 13, 2024 03:43
@ygree ygree marked this pull request as ready for review February 13, 2024 04:57
@ygree ygree requested a review from a team February 13, 2024 04:57
@ygree ygree requested review from a team as code owners February 13, 2024 04:57
@ygree ygree requested a review from Kyle-Verhoog February 13, 2024 04:59
Copy link
Member

@Kyle-Verhoog Kyle-Verhoog left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

a couple nits, but otherwise lgtm

assert cfg_state["apply_state"] == 3
assert cfg_state["apply_error"] != ""

@missing_feature(context.library in ["golang"], reason="Not implemented yet")
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
@missing_feature(context.library in ["golang"], reason="Not implemented yet")

I think we can rely on the manifest for skipping golang

Copy link
Contributor Author

@ygree ygree Feb 13, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not really! Go tracer does a case-sensitive check, so I added this annotation to exclude Go Tracer from this test case only and not from the entire test class.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

oh I see! Yep that makes sense then. Maybe we should update the reason to include that context?

@ygree ygree force-pushed the ygree/remote-config-svc-env-check branch from 008c45c to fa492e4 Compare February 13, 2024 21:29
…e-insensitivity test

Split TestDynamicConfigV1 and TestDynamicConfigIgnoreMismatchingTargets

Update tests/parametric/test_dynamic_configuration.py
@ygree ygree force-pushed the ygree/remote-config-svc-env-check branch from fa492e4 to 4d9a5c9 Compare February 13, 2024 21:30
@ygree ygree merged commit 809ce63 into main Feb 14, 2024
@ygree ygree deleted the ygree/remote-config-svc-env-check branch February 14, 2024 18:49
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.

4 participants