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
fix(rcm): store payloads target files content (#5270)
Remote Configuration should be able to store previous products target
file content due to ASM needs to update all content/rules, the new once
and the previous once.
further more, if a RC target file is disabled, RC should remove all
configuration related to this target_file.
(Note: this bug was introduced with the new products in 1.10 so there is
no need to backport).
e.g:
## Actual behavior:
- Payload1:
- Product `ASM_DD`. New target file `ASM_DD/file_12`. Content:
`{"exclusions": [rule1]}`
- ASM WAF updates with: `{"exclusions": [rule1]}`
- Payload2:
- Product `ASM_DD`. New target file `ASM_DD/file_34`. Content:
`{"exclusions": [rule2]}`
- ASM WAF updates with: `{"exclusions": [rule2]}`
- Payload3:
- Product `ASM_DD`. Disable Target File `ASM_DD/file_34`. Content:
`{"exclusions": [rule2]}`
- ASM WAF updates with: `{"exclusions": []}`
## With this PR the new behavior is:
- Payload1:
- Product `ASM_DD`. New target file `ASM_DD/file_12`. Content:
`{"exclusions": [rule1]}`
- ASM WAF updates with: `{"exclusions": [rule1]}`
- Payload2:
- Product `ASM_DD`. New target file `ASM_DD/file_34`. Content:
`{"exclusions": [rule2]}`
- ASM WAF updates with: `{"exclusions": [rule1, rule2]}`
- Payload3:
- Product `ASM_DD`. Disable Target File `ASM_DD/file_34`. Content:
`{"exclusions": [rule2]}`
- ASM WAF updates with: `{"exclusions": [rule1]}`
## Affected versions
1.10.rcX
## 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/contributing.html#Release-Note-Guidelines)
are followed.
- [x] Documentation is included (in-code, generated user docs, [public
corp docs](https://github.com/DataDog/documentation/)).
- [x] Author is aware of the performance implications of this PR as
reported in the benchmarks PR comment.
## Reviewer Checklist
- [x] Title is accurate.
- [x] No unnecessary changes are introduced.
- [x] Description motivates each change.
- [x] Avoids breaking
[API](https://ddtrace.readthedocs.io/en/stable/versioning.html#interfaces)
changes unless absolutely necessary.
- [x] Testing strategy adequately addresses listed risk(s).
- [x] Change is maintainable (easy to change, telemetry, documentation).
- [x] Release note makes sense to a user of the library.
- [x] Reviewer is aware of, and discussed the performance implications
of this PR as reported in the benchmarks PR comment.
---------
Co-authored-by: Juanjo Alvarez Martinez <[email protected]>
Co-authored-by: Christophe Papazian <[email protected]>
0 commit comments