Implement run-method on KiotaRequestAdapterHook and move logic away from triggerer to hook #39237
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.
Moved the logic which calls the MSGraph endpoint from MSGraphTrigger to the run-method of the KiotaRequestAdapterHook. That way we have the same approach as with the HttpHook and HttpOperator as in the future the dream would be that both could become one. This is also in line with the wanted approach in Airflow to have less operators (e.g. thus more generic one) which can use interchangeable hooks to achieve the same goal but with less operators (and thus more specialized hooks).
The Hook will also handle HTTP statuc codes from the response, if not valid the corresponding AirflowException will be thrown.
^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named
{pr_number}.significant.rst
or{issue_number}.significant.rst
, in newsfragments.