Skip to content

Merge APPSEC_REQUEST_BLOCKING scenario into APPSEC_BLOCKING_FULL_DENYLIST#5277

Merged
jandro996 merged 2 commits into
mainfrom
alejandro.gonzalez/remove-APPSEC_REQUEST_BLOCKING-scenario
Sep 23, 2025
Merged

Merge APPSEC_REQUEST_BLOCKING scenario into APPSEC_BLOCKING_FULL_DENYLIST#5277
jandro996 merged 2 commits into
mainfrom
alejandro.gonzalez/remove-APPSEC_REQUEST_BLOCKING-scenario

Conversation

@jandro996

Copy link
Copy Markdown
Member

Motivation

As the system-tests repository grows, we need to ensure efficient test matrix management by preventing duplicate scenarios and identifying opportunities to merge similar EndToEnd scenarios. Duplicate scenarios waste CI resources and increase maintenance overhead without providing additional test coverage.

Changes

remove APPSEC_REQUEST_BLOCKING scenario and replace annotated tests with APPSEC_BLOCKING_FULL_DENYLIST

Workflow

  1. ⚠️ Create your PR as draft ⚠️
  2. Work on you PR until the CI passes
  3. Mark it as ready for review
    • Test logic is modified? -> Get a review from RFC owner.
    • Framework is modified, or non obvious usage of it -> get a review from R&P team

🚀 Once your PR is reviewed and the CI green, you can merge it!

🛟 #apm-shared-testing 🛟

Reviewer checklist

  • If PR title starts with [<language>], double-check that only <language> is impacted by the change
  • No system-tests internal is modified. Otherwise, I have the approval from R&P team
  • A docker base image is modified?
    • the relevant build-XXX-image label is present
  • A scenario is added (or removed)?

@jandro996
jandro996 marked this pull request as ready for review September 17, 2025 14:12
@jandro996
jandro996 requested review from a team as code owners September 17, 2025 14:12

@cbeauchesne cbeauchesne left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

@jandro996

Copy link
Copy Markdown
Member Author

Ahh sorry! I already updated the system-tests side, but I didn’t realize some tracers have references to the scenarios in their own projects… Any idea how to orchestrate this? I guess we need to remove those references from the tracers first, and only then update the system-tests. Am I right?

@jandro996
jandro996 force-pushed the alejandro.gonzalez/remove-APPSEC_REQUEST_BLOCKING-scenario branch from 1d702a5 to 5ba02ca Compare September 22, 2025 08:15

@cbeauchesne cbeauchesne left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

AGTM

@@ -2513,110 +2513,6 @@
"uds-sinatra": 44

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

For future PR, no need to change this file, it's automatically generated

@jandro996
jandro996 merged commit 141e613 into main Sep 23, 2025
2088 checks passed
@jandro996
jandro996 deleted the alejandro.gonzalez/remove-APPSEC_REQUEST_BLOCKING-scenario branch September 23, 2025 14:20
jandro996 added a commit to DataDog/dd-trace-rb that referenced this pull request Sep 24, 2025
…L_DENYLIST in ST (#4910)

What does this PR do?
This PR just cleans up the pipeline by removing the reference to the no-longer-existing scenario.

Motivation:
The scenario APPSEC_REQUEST_BLOCKING has been merged into APPSEC_BLOCKING_FULL_DENYLIST in the system-tests project. This means tests that were previously run under APPSEC_REQUEST_BLOCKING will now execute using APPSEC_BLOCKING_FULL_DENYLIST (DataDog/system-tests#5277)
jandro996 added a commit to DataDog/dd-trace-py that referenced this pull request Sep 24, 2025
## Description

The scenario APPSEC_REQUEST_BLOCKING has been merged into
APPSEC_BLOCKING_FULL_DENYLIST in the system-tests project. This means
tests that were previously run under APPSEC_REQUEST_BLOCKING will now
execute using APPSEC_BLOCKING_FULL_DENYLIST
(DataDog/system-tests#5277)

This PR just cleans up the pipeline by removing the reference to the
no-longer-existing scenario and updates ST version

## Testing

<!-- Describe your testing strategy or note what tests are included -->

## Risks

<!-- Note any risks associated with this change, or "None" if no risks
-->

## Additional Notes

<!-- Any other information that would be helpful for reviewers -->
chagui pushed a commit that referenced this pull request Oct 1, 2025
…LIST (#5277)

Motivation
As the system-tests repository grows, we need to ensure efficient test matrix management by preventing duplicate scenarios and identifying opportunities to merge similar EndToEnd scenarios. Duplicate scenarios waste CI resources and increase maintenance overhead without providing additional test coverage.

Changes
remove APPSEC_REQUEST_BLOCKING scenario and replace annotated tests with APPSEC_BLOCKING_FULL_DENYLIST
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.

2 participants