-
Notifications
You must be signed in to change notification settings - Fork 377
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
[APPSEC-56188] Replace Scope with Context #4277
base: master
Are you sure you want to change the base?
Conversation
Datadog ReportBranch report: ❌ 12 Failed (0 Known Flaky), 22186 Passed, 1476 Skipped, 4m 51.62s Total Time ❌ Failed Tests (12)
|
BenchmarksBenchmark execution time: 2025-01-10 16:44:21 Comparing candidate commit 4c768f4 in PR branch Found 0 performance improvements and 0 performance regressions! Performance is the same for 31 metrics, 2 unstable metrics. |
5ec6575
to
615da95
Compare
615da95
to
4c768f4
Compare
What does this PR do?
Replace irresponsible class
AppSec::Scope
withAppSec::Context
and move some functionality into it.Motivation:
In order to implement RASP/WAF telemetry and metrics we need to adjust the domain of the AppSec. The main point -
AppSec::Context
represents request context and hides complexity of the security engine calls (and gathering statistics) from the instrumentation.You will see some obvious issues with existing code because of that change, but that's the plan. We move slowly with a guaranteed compatibility.
Change log entry
No.
Additional Notes:
This is the first PR which establishes the base to develop metrics collection. In this PR introduces as minimum as possible changes to stay compatible, but move forward.
How to test the change?
CI (specifically systems tests) should be enough.