use the 202 status consistently in triggering endpoints #2224
Open
nhoening wants to merge 2 commits into
Open
Conversation
… scheduling) and provide follow-up URLs in the response Signed-off-by: Nicolas Höning <nicolas@seita.nl>
…ished (just like get_forecast) - for now only use this (over the old 400 code) if API_SUNSET is being used Signed-off-by: Nicolas Höning <nicolas@seita.nl>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Use 202 in triggering endoints (forecasting scheduling) and provide follow-up URLs in the response.
Closes #2171
documentation/changelog.rstLook & Feel
Mainly Sphinx and Swaggerdocs.
How to test
Further Improvements