-
Notifications
You must be signed in to change notification settings - Fork 409
[datadog_synthetics_test] Support the blockedRequestPatterns
option for browser tests
#3257
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
[datadog_synthetics_test] Support the blockedRequestPatterns
option for browser tests
#3257
Conversation
9864506
to
1c32d2e
Compare
761ae2f
to
2825044
Compare
Signed-off-by: Katia SHANG <katia.shang@datadoghq.com>
Signed-off-by: Katia SHANG <katia.shang@datadoghq.com>
Signed-off-by: Katia SHANG <katia.shang@datadoghq.com>
2825044
to
86a8ef9
Compare
Signed-off-by: Katia SHANG <katia.shang@datadoghq.com>
Signed-off-by: Katia SHANG <katia.shang@datadoghq.com>
…g into katia.shang/add-blockedrequestpatterns
…en_id computed following API changes
blockedRequestPatterns
option for browser tests
/merge |
View all feedbacks in Devflow UI.
This merge request is not mergeable according to GitHub. Common reasons include pending required checks, missing approvals, or merge conflicts — but it could also be blocked by other repository rules or settings.
The expected merge time in
|
This PR adds support for the
blockedRequestPatterns
option for browser tests.api-spec PR: Add blockedRequestPatterns
While updating recording for tests accordingly, we noticed a change in behaviour for RUM settings which was causing the tests to fail. In our public APIs where the fields
application_id
andclient_token_id
are now auto-generated if RUM is enabled and the user does not explicitly set them.These fields are updated to optional computed fields accordingly.