Will-Lo opened a new pull request, #3516: URL: https://github.com/apache/gobblin/pull/3516
Dear Gobblin maintainers, Please accept this PR. I understand that it will not be reviewed until I have checked off all the steps below! ### JIRA - [x] My PR addresses the following [Gobblin JIRA](https://issues.apache.org/jira/browse/GOBBLIN/) issues and references them in the PR title. For example, "[GOBBLIN-XXX] My Gobblin PR" - https://issues.apache.org/jira/browse/GOBBLIN-1656 ### Description - [x] Here are some details about my PR, including screenshots (if applicable): GaaS supports user and flowgroup quotas. When a user wants to create a flow that runs immediately (adhoc or scheduled) it should not run if the quota is exceeded (this is built in already). Additionally, the user's request should fail, and return a different http status code (in this PR it's 503) so that the clients can know when the flow will not run and handle the exceeded scenario. When a user updates a scheduled flowConfig that runs immediately -> It will reject the flow configuration update and not run the job When a user creates an adhoc flow -> the job will be rejected entirely ### Tests - [x] My PR adds the following unit tests __OR__ does not need testing for this extremely good reason: ### Commits - [x] My commits all reference JIRA issues in their subject lines, and I have squashed multiple commits if they address the same issue. In addition, my commits follow the guidelines from "[How to write a good git commit message](http://chris.beams.io/posts/git-commit/)": 1. Subject is separated from body by a blank line 2. Subject is limited to 50 characters 3. Subject does not end with a period 4. Subject uses the imperative mood ("add", not "adding") 5. Body wraps at 72 characters 6. Body explains "what" and "why", not "how" -- 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]
