<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=496527) </details> <!--IssueSummary end--> <!-- This template is a great use for issues that are feature::additions or technical tasks for larger issues.--> ### Proposal When API call it made to protect a tag which is already protected, GitLab returns the message : `Name has already been taken`. However, when running automations like [GitLabForm](https://gitlabform.github.io/gitlabform/), it's difficult to know at which tag the automation failed due to existing protected tag. For example, the following API call marks the tag `test` as protected and executes without any issues: ``` > curl --request POST \ --header "PRIVATE-TOKEN: $PJ_TAG" \ --header "Content-Type: application/json" \ --data '{"name": "test", "create_access_level": "40"}' \ "https://gitlab.com/api/v4/projects/XYZ/protected_tags" {"name":"test","create_access_levels":[{"id":XYZ,"access_level":40,"access_level_description":"Maintainers","deploy_key_id":null,"user_id":null,"group_id":null}]}% ``` However, if I run the same API call again, I get the error Name has already been taken : ``` > curl --request POST \ --header "PRIVATE-TOKEN: $PJ_TAG" \ --header "Content-Type: application/json" \ --data '{"name": "test", "create_access_level": "40"}' \ "https://gitlab.com/api/v4/projects/XYZ/protected_tags" {"message":["Name has already been taken"]}% ``` Looking at the [GitLab source code](https://gitlab.com/gitlab-org/gitlab/-/blob/master/spec/requests/api/protected_tags_spec.rb#L163) and this is an expected behaviour. However, it would be really helpful if we can include the entity (in this case the tag name) which is failing the API call. Customer request (Zendesk ticket) : https://gitlab.zendesk.com/agent/tickets/568428 (Internal URL) <!-- Use this section to explain the feature and how it will work. It can be helpful to add technical details, design proposals, and links to related epics or issues. --> <!-- Consider adding related issues and epics to this issue. You can also reference the Feature Proposal Template (https://gitlab.com/gitlab-org/gitlab/-/blob/master/.gitlab/issue_templates/Feature%20proposal%20-%20detailed.md) for additional details to consider adding to this issue. Additionally, as a data oriented organization, when your feature exits planning breakdown, consider adding the `What does success look like, and how can we measure that?` section. --> <!-- Label reminders Use the following resources to find the appropriate labels: - Use only one tier label choosing the lowest tier this is intended for - https://gitlab.com/gitlab-org/gitlab/-/labels - https://about.gitlab.com/handbook/product/categories/features/ -->