Add HEAD endpoint to group relations export API
What does this MR do?
This MR adds new HEAD endpoint to group relations export API. It's going to be used in the future MR as part of #329864 (closed) It's used in !61044 (closed) draft MR but since change is big I am splitting it into multiple ones.
The idea is when we want to download and import such relations we're going to hit this endpoint before downloading the file to make sure it has acceptable type and size.
One thing to note: Grape v 1.5.3 added routing of HEAD requests to GET endpoints by default, however we use Grape 1.5.2 which does not have such capability, hence a new endpoint addition is required.
Mentions #329864 (closed)
Screenshots (strongly suggested)
Does this MR meet the acceptance criteria?
Conformity
-
I have included a changelog entry, or it's not needed. (Does this MR need a changelog?) -
I have added/updated documentation, or it's not needed. (Is documentation required?) -
I have properly separated EE content from FOSS, or this MR is FOSS only. (Where should EE code go?) -
I have added information for database reviewers in the MR description, or it's not needed. (Does this MR have database related changes?) -
I have self-reviewed this MR per code review guidelines. -
This MR does not harm performance, or I have asked a reviewer to help assess the performance impact. (Merge request performance guidelines) -
I have followed the style guides.
Availability and Testing
-
I have added/updated tests following the Testing Guide, or it's not needed. (Consider all test levels. See the Test Planning Process.) -
I have tested this MR in all supported browsers, or it's not needed. -
I have informed the Infrastructure department of a default or new setting change per definition of done, or it's not needed.
Security
Does this MR contain changes to processing or storing of credentials or tokens, authorization and authentication methods or other items described in the security review guidelines? If not, then delete this Security section.
-
Label as security and @ mention @gitlab-com/gl-security/appsec -
The MR includes necessary changes to maintain consistency between UI, API, email, or other methods -
Security reports checked/validated by a reviewer from the AppSec team