You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
New API Security features:
- Use last version of appsec event rules to provides static rules for
api security
- Remove temporary rule file previously used for api security
- Add remote config support for api security (ability to remotely update
scanners and processors from RC) (api security sample rate was already
added in a previous PR)
- Update api security unit tests accordingly
API Security is still a private feature, no release note for now.
## Checklist
- [x] Change(s) are motivated and described in the PR description.
- [x] Testing strategy is described if automated tests are not included
in the PR.
- [x] Risk is outlined (performance impact, potential for breakage,
maintainability, etc).
- [x] Change is maintainable (easy to change, telemetry, documentation).
- [x] [Library release note
guidelines](https://ddtrace.readthedocs.io/en/stable/releasenotes.html)
are followed. If no release note is required, add label
`changelog/no-changelog`.
- [x] Documentation is included (in-code, generated user docs, [public
corp docs](https://github.com/DataDog/documentation/)).
- [x] Backport labels are set (if
[applicable](https://ddtrace.readthedocs.io/en/latest/contributing.html#backporting))
## Reviewer Checklist
- [ ] Title is accurate.
- [ ] No unnecessary changes are introduced.
- [ ] Description motivates each change.
- [ ] Avoids breaking
[API](https://ddtrace.readthedocs.io/en/stable/versioning.html#interfaces)
changes unless absolutely necessary.
- [ ] Testing strategy adequately addresses listed risk(s).
- [ ] Change is maintainable (easy to change, telemetry, documentation).
- [ ] Release note makes sense to a user of the library.
- [ ] Reviewer has explicitly acknowledged and discussed the performance
implications of this PR as reported in the benchmarks PR comment.
- [ ] Backport labels are set in a manner that is consistent with the
[release branch maintenance
policy](https://ddtrace.readthedocs.io/en/latest/contributing.html#backporting)
- [ ] If this PR touches code that signs or publishes builds or
packages, or handles credentials of any kind, I've requested a review
from `@DataDog/security-design-and-guidance`.
- [ ] This PR doesn't touch any of that.
---------
Signed-off-by: Juanjo Alvarez <[email protected]>
Co-authored-by: Emmett Butler <[email protected]>
Co-authored-by: Yun Kim <[email protected]>
Co-authored-by: Tahir H. Butt <[email protected]>
Co-authored-by: Alberto Vara <[email protected]>
Co-authored-by: Kyle Verhoog <[email protected]>
Co-authored-by: Zachary Groves <[email protected]>
Co-authored-by: Federico Mon <[email protected]>
Co-authored-by: Romain Komorn <[email protected]>
Co-authored-by: Eric Navarro <[email protected]>
Co-authored-by: Emmett Butler <[email protected]>
Co-authored-by: Juanjo Alvarez Martinez <[email protected]>
Co-authored-by: Brett Langdon <[email protected]>
Co-authored-by: AJ Stuyvenberg <[email protected]>
Co-authored-by: Munir Abdinur <[email protected]>
Co-authored-by: Gabriele N. Tornetta <[email protected]>
Co-authored-by: HovhannesV <[email protected]>
Co-authored-by: Tahir H. Butt <[email protected]>
0 commit comments