AWS Connection Docs: Remove deprecation information due to undeprecate wrong aws_conn_id fallback behaviour
#33636
Conversation
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
boring-cyborg
bot
added
area:providers
kind:documentation
provider:amazon
Taragolis
changed the title
depreciation information due to undeprecate wrong aws_conn_id fallback behaviouraws_conn_id fallback behaviour
Member
|
Depreciation? Deprecation? |
Taragolis
changed the title
aws_conn_id fallback behaviouraws_conn_id fallback behaviour
Taragolis
force-pushed
the
aws-docs-actualisation
branch
2 times, most recently
from
344414b to
6584c9d
Compare
eladkal
reviewed
Aug 23, 2023
…e wrong `aws_conn_id` fallback behaviour
Taragolis
force-pushed
the
aws-docs-actualisation
branch
from
6584c9d to
69c12b7
Compare
o-nikolas
reviewed
Aug 23, 2023
Co-authored-by: Niko Oliveira <onikolas@amazon.com>
potiuk
approved these changes
Aug 23, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
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.
Due to changes in #30806 notice about deprecation behaviour in documentation doesn't make any sense.
^ 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.