AWS codebuild documentation change
Summary
Added multiple JSON section dividers and formatting elements throughout the document
Security assessment
The changes appear to be formatting/structural updates adding JSON section markers and horizontal rules (****). No security-related content changes, vulnerability fixes, or security feature documentation were introduced. The modifications are purely presentational without altering security context or policies.
Diff
diff --git a/codebuild/latest/userguide/action-context-keys.md b/codebuild/latest/userguide/action-context-keys.md index 8a42b5a52..09d4a7def 100644 --- a//codebuild/latest/userguide/action-context-keys.md +++ b//codebuild/latest/userguide/action-context-keys.md @@ -31,0 +32,6 @@ This policy allows the caller to use the selected VPCs, subnets, and security gr +JSON + + +**** + + @@ -68,0 +76,6 @@ The `codebuild:source.buildspec` condition key supports only the Null operator t +JSON + + +**** + + @@ -91,0 +106,6 @@ This policy allows creating fleets that can build with only `c5.large` or `m5.la +JSON + + +**** + + @@ -110,0 +132,6 @@ This policy allows the caller to override the `STAGE` environment variable to be +JSON + + +**** + + @@ -153,0 +182,6 @@ You can use variables in condition key names like `secondarySources/${sourceIden +JSON + + +**** + + @@ -174,0 +210,6 @@ CodeBuild supports condition keys to check the existence of some fields in the A +JSON + + +**** + +