pvillard31 opened a new pull request, #10230: URL: https://github.com/apache/nifi/pull/10230
# Summary NIFI-14886 - GitLab Registry Client - switch from Repository File API to Commit API I have reproduced the issue mentioned in the JIRA where the error starts when a flow to be versioned is around 2.5MB. It looks like the Repository File API is using a PUT where the payload is URL encoded as query params. The Commit API on the other hand is doing a POST where the flow content is part of a larger JSON payload. I confirmed that I was able to commit versioned flows well over 10MB+ (the limit would likely be a timeout or some limits on the GitLab side now). # Tracking Please complete the following tracking steps prior to pull request creation. ### Issue Tracking - [ ] [Apache NiFi Jira](https://issues.apache.org/jira/browse/NIFI) issue created ### Pull Request Tracking - [ ] Pull Request title starts with Apache NiFi Jira issue number, such as `NIFI-00000` - [ ] Pull Request commit message starts with Apache NiFi Jira issue number, as such `NIFI-00000` ### Pull Request Formatting - [ ] Pull Request based on current revision of the `main` branch - [ ] Pull Request refers to a feature branch with one commit containing changes # Verification Please indicate the verification steps performed prior to pull request creation. ### Build - [ ] Build completed using `./mvnw clean install -P contrib-check` - [ ] JDK 21 ### Licensing - [ ] New dependencies are compatible with the [Apache License 2.0](https://apache.org/licenses/LICENSE-2.0) according to the [License Policy](https://www.apache.org/legal/resolved.html) - [ ] New dependencies are documented in applicable `LICENSE` and `NOTICE` files ### Documentation - [ ] Documentation formatting appears as expected in rendered files -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
