git.security.resolve-secret-alertSay what was done about a bypassed secret (revoked, false positive, …)
Request syntax
PATCH /git/api/repositories/{repoId}/security/secret-alerts/{alertId}
{
"resolution": "enum",
"comment": "string"
}Path parameters
repoIdRequiredstring
Constraints: uuid
alertIdRequiredstring
Constraints: uuid
Request body
resolutionRequiredenum
What was done about the secret that was pushed
One of:
revoked,false_positive,used_in_tests,wont_fixcommentOptionalstring
A note on the resolution, in your own words
Constraints: max 2000 chars
Response
200 with the alert, resolved: resolution, resolutionComment, resolvedByIamUserId, resolvedAt. 404 for an alert that was not bypassed.
A JSON response is wrapped as { "success": true, "data": … }; the CLI prints the whole body with --json.
Fields of data
idAlwaysstring
The alertorgIdAlwaysstring
The organizationrepoIdAlwaysstring
The repositorystateAlwaysone of blocked, bypassed, resolved
blocked: the push was refused; bypassed: pushed anyway and in the history; resolved: someone said what was doneruleIdAlwaysstring
The detector that matchedruleNameAlwaysstring
The kind of credential, in wordspathAlwaysstring
The file the secret is inlineAlwaysnumber
The line it is on, from 1blobOidAlwaysstring
The id of the file content it was found inrefNameAlwaysstring
The ref that was pushedcommitOidAlwaysstring
The pushed tip of the ref; the secret is in its historyfingerprintAlwaysstring
A sha256 fingerprint to recognise the same secret againpreviewAlwaysstring
A redacted preview; never the secret itselfpushedByAlwaysstring
Who pushed: user:<IAM user id>, deploy:<deploy key id> or unknownpushedByIamUserIdAlwaysstring, may be null
The IAM user who pushed; null for a deploy key or a deleted userbypassReasonAlwaysstring, may be null
Why it was pushed anyway; null unless bypassedresolutionAlwaysone of revoked, false_positive, used_in_tests, wont_fix, may be null
What was done about it; null until resolvedresolutionCommentAlwaysstring, may be null
A note on the resolution, if anyresolvedByIamUserIdAlwaysstring, may be null
Who resolved it; null until resolvedresolvedAtAlwaysstring, may be null
When it was resolved (ISO 8601); null until thencreatedAtAlwaysstring
When the push was scanned (ISO 8601)updatedAtAlwaysstring
When the alert last changed (ISO 8601)
Checked against the handlers: every route test validates their answers against this schema.
Errors
- 400The request does not pass the schema above. The body is { "error": …, "issues": […] }, one issue per field.
- 401No credentials, or an access key that is unknown, revoked or expired.
- 403The caller's policies do not allow git:UpdateSecurityAlert on this resource. The body names the action and the resource, and the refusal is recorded in the audit log.
- 404The resource does not exist in your organization.
Examples
The required parameters only, with example values. Replace id and the other placeholders with your own.
dcloud git security resolve-secret-alert repoId alertId --resolution revokedcurl -X PATCH "https://console.platform-development.deutschecloud.app/git/api/repositories/repoId/security/secret-alerts/alertId" \
-H "Authorization: EWS-ACCESS-KEY $ACCESS_KEY" \
-H "Content-Type: application/json" \
-d '{"resolution":"revoked"}'Generated from the API description, the same one the API checks requests against and the CLI is built from. MCP tool: dcloud_git_security_resolve-secret-alert.