Prepare docs for new providers release (August 2022) #25618
Conversation
|
cc: @vincbeck @ferruzzi @alexott @wojsamjan -> please take a look and see if there is anything else we should include |
|
lgtm for Databricks side, only maybe we don't need this one: |
I prefer to keep full list of the "code" changes. that have potential to change behaviours of released code (As opposed to changes that just impact test code/documentation which can be "hidden") - having the PR# in changelog is good way to find out problem reasons when they happen. |
|
And mostly they make communication with users easier. Changelog is essenially a "communication" tool with the users - it is easier to explain to user "this change was done, impacted this and actually you can see it there - it was mentioned there in the changelog" |
|
ok |
|
cc: @lwyszomi too |
|
Yep. Just approved and merged it. |
|
I was hoping to get #25413 in this one since it'll be a major release for Amazon. |
I'm not sure how this one will be a breaking change? |
|
It's also removing deprecated code, so I figured this was a good time. I just pushed a change that is passing all local testing, so we'll see. No need to hold up the release if you don't think it's important to get it in before the major. |
|
#18896 is probably also in the waiting list for next wave? |
Merged. |
6aadd0f
to
6db5c4d
Compare
|
Updated, and reeady for merging when green. |
|
I need +1 here :) |
| * ``Remove deprecated modules (#25543)`` | ||
| * ``Resolve Amazon Hook's 'region_name' and 'config' in wrapper (#25336)`` | ||
| * ``Resolve and validate AWS Connection parameters in wrapper (#25256)`` | ||
| * ``Standardize AwsLambda (#25100)`` |
There was a problem hiding this comment.
AwsLambda is not a breaking change #25100
It's backward compatible and the deprecation of this class/modules were not removed in Vincent PRs
#25543 (comment) , #25609 (comment)
^ 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.rstor{issue_number}.significant.rst, in newsfragments.