DOCS-11221: Move IaC docs to Code Security #29947
Merged
Conversation
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
drichards-87
added
WORK IN PROGRESS
✅ Documentation Team ReviewThe documentation team has approved this pull request. Thank you for your contribution! |
Preview links (active after the
|
michaelcretzman
requested changes
Jun 20, 2025
Comment on lines
24
to
33
| ## Key capabilities | ||
|
|
||
| With IaC Security, you can: | ||
|
|
||
| - Scan Terraform files for security misconfigurations | ||
| - Surface IaC misconfigurations in the Code Security Vulnerabilities tab | ||
| - Group and filter findings by severity, triage status, and other facets | ||
| - View detailed remediation guidance and code snippets for each finding | ||
| - Track finding status and history for triage and resolution | ||
| - Configure scanning exclusions |
There was a problem hiding this comment.
this is essentially a bulleted list of the introductory paragraph. My suggestion is to keep the opening intro sentence ("Infrastructure as Code (IaC) Security automatically analyzes your Terraform files for security misconfigurations.") and then just using the bulleted list. Skip the paragraph.
| ## Getting started | ||
|
|
||
| 1. [Set up IaC Security][1] in your environment | ||
| 2. Configure [scanning exclusions][2] if needed |
There was a problem hiding this comment.
how do they know if they need this?
There was a problem hiding this comment.
Good point. I'll update the description.
Co-authored-by: Michael Cretzman <58786311+michaelcretzman@users.noreply.github.com>
drichards-87
added
editorial review
michaelcretzman
approved these changes
Jun 23, 2025
aaxzheng
approved these changes
Jun 23, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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?
DOCS-11221.
Merge instructions
Merge readiness:
For Datadog employees:
Your branch name MUST follow the
<name>/<description>convention and include the forward slash (/). Without this format, your pull request will not pass CI, the GitLab pipeline will not run, and you won't get a branch preview. Getting a branch preview makes it easier for us to check any issues with your PR, such as broken links.If your branch doesn't follow this format, rename it or create a new branch and PR.
[6/5/2025] Merge queue has been disabled on the documentation repo. If you have write access to the repo, the PR has been reviewed by a Documentation team member, and all of the required checks have passed, you can use the Squash and Merge button to merge the PR. If you don't have write access, or you need help, reach out in the #documentation channel in Slack.
Additional notes