[SDS-1788] support additional SDS Secondary Validators#788
Conversation
jamesphlewis
left a comment
There was a problem hiding this comment.
tentative approval, let's test from staging (with the new API response) and production (with the old API response) first before merging to ensure we don't break backwards compat.
Testing SummaryTo verify the new V2 version of the Secret Rule Validator API field (https://github.com/DataDog/dd-source/pull/304183) and ensure backward compatibility with the
In these tests, I added a new test secret that matches with the main branch of |
|
/merge |
|
View all feedbacks in Devflow UI.
The expected merge time in
Tests failed on this commit 616ea2c: What to do next?
|
|
/merge |
|
View all feedbacks in Devflow UI.
The expected merge time in
Tests failed on this commit fca2709: What to do next?
|
|
/merge |
|
View all feedbacks in Devflow UI.
The expected merge time in
Tests failed on this commit b57c996: What to do next?
|
|
/merge |
|
View all feedbacks in Devflow UI.
The expected merge time in
|
What problem are you trying to solve?
Currently in
convert_to_sds_ruleconfig, the only validator that is getting applied from the SDS configurations isJwtExpirationChecker. However, the current version of the sds library supports more validators for Secrets (i.eGithubTokenChecksum).What is your solution?
This PR updates the
convert_to_sds_ruleconfigfunction to configure all validators that are supported in the sds library version.Alternatives considered
What the reviewer should know
Validation