AWS configuration parameters cannot be overwritten

[DrGFreeman]

While AWS configuration parameters can be set via a config file or environment variables, there may be cases where these parameters need to be overwritten.

The current put_df, get_df and transactions module functions do not provide a mean to pass these parameters.

Adding a **kwargs argument to the different functions and passing it to the underlying boto3.client or boto3.resource function call would provide this functionality.

For examples, the get_df function signature would become:

def get_df(*, table, keys=None, attributes=None, dtype=None, **resource_kwargs):
    ...

[sreyan-ghosh]

Hi @DrGFreeman, so first 2 changes need to be made in the dynamo_pandas/dynamo_pandas.py file.

These functions need to have **kwargs added, so as per your example, should all of them have **resource_kwargs added or **client_kwargs also?

Would the following be correct?

• get_df

def get_df(*, table, keys=None, attributes=None, dtype=None, **resource_kwargs):
    """Get items from a table into a dataframe."""

• put_df

def put_df(df, *, table, **resource_kwargs):
    """Put rows of a dataframe as items into a table. If the item(s) do not exist in the"""

[DrGFreeman]

Hi @sreyan-ghosh, thanks for your interest! For you info, I have already started working on this. I just assigned myself the issue to avoid confusion.

Regarding your question, I've settled to use a boto3_kwargs parameter to all the functions where it is applicable. Since both the boto3.client() and boto3.resource() function calls share the same parameters, this will leave the possibility to refactor the functions and change between boto3.client and boto3.resource internally without affecting existing code making use of the boto3_kwargs parameter.

[sreyan-ghosh]

Aah I see, so boto3_kwargs is like a super wrapper for boto3.client and boto3.resource. No worries, it's all a learning experience for me. Thanks for the descriptive answer @DrGFreeman 😄