[K9CODESEC-4729] Document the Secret Scanning configuration file - #39313
Open
MikaYuoadas wants to merge 1 commit into
Open
[K9CODESEC-4729] Document the Secret Scanning configuration file#39313MikaYuoadas wants to merge 1 commit into
MikaYuoadas wants to merge 1 commit into
Conversation
Adds the secrets.global-config fields to the Secret Scanning page and schema-version v1.5 to the Code Security configuration reference. Refs: K9CODESEC-4729
Contributor
Preview links (active after the
|
maycmlee
reviewed
Aug 19, 2026
maycmlee
left a comment
maycmlee
left a comment
Contributor
There was a problem hiding this comment.
Looks great, just a small suggestion!
|
|
||
| ## File configuration | ||
|
|
||
| Rules are configured in Datadog, as described above. Which files Secret Scanning reads is configured under the `secrets` key in the Code Security configuration. Define it in Datadog, or in a `code-security.datadog.yaml` file at the root of your repository. |
Contributor
There was a problem hiding this comment.
It's clearer for users to be linked to the specific section.
Suggested change
| Rules are configured in Datadog, as described above. Which files Secret Scanning reads is configured under the `secrets` key in the Code Security configuration. Define it in Datadog, or in a `code-security.datadog.yaml` file at the root of your repository. | |
| Rules are configured in Datadog as described in the [Configuring rules](#configuring-rules) section. Which files Secret Scanning reads is configured under the `secrets` key in the Code Security configuration. Define it in Datadog, or in a `code-security.datadog.yaml` file at the root of your repository. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What does this PR do? What is the motivation?
Documents the configuration file for Secret Scanning, and adds
schema-version: v1.5to the Code Security configuration reference.Secret Scanning gains a configuration file alongside its existing in-app configuration. Rules, scanning groups, and custom rules continue to be configured in Datadog and the config file controls which files are analyzed.
Secret Scanning configuration page
File configurationsection covering thesecrets.global-configproperties:only-paths,ignore-paths,use-gitignore,ignore-generated-files, andmax-file-size-kb.Rule ConfigurationtoConfiguration, since it covers both rule and file configuration.Code Security configuration reference
v1.5schema version and thesecretssection to the version table, the structure example, and the optional-sections list.Merge readiness