Skip to content

AWS Connection Docs: Remove deprecation information due to undeprecate wrong aws_conn_id fallback behaviour #33636

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
potiuk merged 2 commits into from
Aug 23, 2023
Merged

AWS Connection Docs: Remove deprecation information due to undeprecate wrong aws_conn_id fallback behaviour #33636

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
69c12b7
AWS Connection Docs: Remove deprecation information due to undeprecat…
Taragolis Aug 23, 2023
40c7e4d
Update docs/apache-airflow-providers-amazon/connections/aws.rst
Taragolis Aug 23, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/apache-airflow-providers-amazon/connections/aws.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -60,10 +60,10 @@ automatically the credentials from there.
.. caution:: If you do not run "airflow connections create-default-connections" command,
most probably you do not have ``aws_default``. For historical reasons, the Amazon Provider
components (Hooks, Operators, Sensors, etc.) fallback to the default boto3 credentials strategy
in case of a missing Connection ID. This behaviour is deprecated and will be removed in a future releases.
in case of a missing Connection ID.

If you need to use the default boto3 credential strategy (credentials in environment variables, IAM Profile, etc.)
please provide ``None`` instead of a connection ID.
please provide ``None``, instead of a missing connection ID, to avoid getting a warning in your logs.

.. _howto/connection:aws:configuring-the-connection:

Expand Down