boto3-refresh-session 0.0.26__tar.gz → 0.0.27__tar.gz
Sign up to get free protection for your applications and to get access to all the features.
- {boto3_refresh_session-0.0.26 → boto3_refresh_session-0.0.27}/PKG-INFO +1 -1
- {boto3_refresh_session-0.0.26 → boto3_refresh_session-0.0.27}/boto3_refresh_session/session.py +5 -9
- {boto3_refresh_session-0.0.26 → boto3_refresh_session-0.0.27}/pyproject.toml +1 -1
- {boto3_refresh_session-0.0.26 → boto3_refresh_session-0.0.27}/LICENSE +0 -0
- {boto3_refresh_session-0.0.26 → boto3_refresh_session-0.0.27}/README.md +0 -0
- {boto3_refresh_session-0.0.26 → boto3_refresh_session-0.0.27}/boto3_refresh_session/__init__.py +0 -0
{boto3_refresh_session-0.0.26 → boto3_refresh_session-0.0.27}/boto3_refresh_session/session.py
RENAMED
@@ -6,15 +6,11 @@ object.
|
|
6
6
|
|
7
7
|
.. warning::
|
8
8
|
``AutoRefreshableSession`` was not tested for manually passing hard-coded
|
9
|
-
account credentials to the
|
10
|
-
|
11
|
-
|
12
|
-
|
13
|
-
|
14
|
-
as parameters; it is for that reason the documentation below, and everywhere
|
15
|
-
else, only mentions ``~/.aws/config`` and ``~/.aws/credentials`` for
|
16
|
-
authorization. Since the ``session_kwargs`` and ``client_kwargs`` parameters
|
17
|
-
were not tested, you will need to use those parameters at your own discretion.
|
9
|
+
account credentials to the ``boto3.client`` object! There is an optional
|
10
|
+
``client_kwargs`` parameter available for doing so, which *should* work;
|
11
|
+
however, that cannot be guaranteed as that functionality was not tested.
|
12
|
+
Pass hard-coded credentials with the ``client_kwargs`` parameter at your
|
13
|
+
own discretion.
|
18
14
|
"""
|
19
15
|
__all__ = ["AutoRefreshableSession"]
|
20
16
|
|
File without changes
|
File without changes
|
{boto3_refresh_session-0.0.26 → boto3_refresh_session-0.0.27}/boto3_refresh_session/__init__.py
RENAMED
File without changes
|