git.tag-protection.createProtect a tag pattern
POST /git/api/repositories/{repoId}/tag-protectionIAM git:ManageBranchProtectionChanges stateDestructive
Request syntax
POST /git/api/repositories/{repoId}/tag-protection
{
"pattern": "string"
}Path parameters
repoIdRequiredstring
Constraints: uuid
Request body
patternRequiredstring
Tag name or glob, e.g. v* or release-*; matching tags need git:PushProtectedTag
Constraints: 1-200 chars, /^[A-Za-z0-9._/*+-]+$/
Response
201 with the rule: id, pattern and createdAt. 409 when the pattern is already protected.
A JSON response is wrapped as { "success": true, "data": … }; the CLI prints the whole body with --json.
Fields of data
idAlwaysstring
The rule's idorgIdAlwaysstring
Your organizationrepoIdAlwaysstring
The repository the record belongs topatternAlwaysstring
The protected tag name or glob, e.g. v*createdAtAlwaysstring
When the rule was added (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:ManageBranchProtection 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 tag-protection create repoId --pattern examplecurl -X POST "https://console.platform-development.deutschecloud.app/git/api/repositories/repoId/tag-protection" \
-H "Authorization: EWS-ACCESS-KEY $ACCESS_KEY" \
-H "Content-Type: application/json" \
-d '{"pattern":"example"}'Generated from the API description, the same one the API checks requests against and the CLI is built from. MCP tool: dcloud_git_tag-protection_create.