apache
Amazon Bedrock - Retrieve and RetrieveAndGenerate
Both of these calls are super fast and neither has any kind of waiter or means of checking the status, so here can not be any sensor or trigger for them. They are simple client calls, but I think making these Operators allowed us to simplify the complicated formatting on the client API call itself, for a better UX.
One question I have is the parameter name for input and query. I feel like these should be standardized, but also we usually go out of our way to stick as close as possible to the API call's parameter names. Let me know what you think. For InvokeModel I used "input_data", I could standardize all three on that name or just leave them as I have here.
All related unit tets, CI, and build-docs pass locally.
^ 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.
