You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In addition, would you be open to including the AWS Auth features as a package extra rather than being included in the core lib (happy to put in a PR). That way the core functionality of this library can depend on as little as possible.
We'd like to use this SDK, but with the current requirements it has pinned it's not possible and we need to revert to using requests.
The text was updated successfully, but these errors were encountered:
Good catch on the urllib3 package, this is defiantly not a hard requirement, and we can get this removed.
In regards to the AWS Auth, are you proposing that we release a new package entirely?
I would be leaning towards keeping all the SDK fully functional as-is. Which package requirement(s) are limiting you? Perhaps we can allow for a wider range of versions instead.
In regards to the AWS Auth, are you proposing that we release a new package entirely?
No, I was thinking something along the lines of package extras so a statement like
pip install infisicalsdk
would install the package core functionality (say, only relies on requests). Then a statement like:
pip install infisicalsdk[aws]
would install the extras like botocore that are required for AWS auth. Appreciate this might not be a route you want to go down though given it would introduce a breaking change
The urllib3 requirement is rather restrictive given that it's only direct usage seems to be here
Would it be possible to unpin this requirement and allow it to follow the conventions of the botocore library?
https://github.com/boto/botocore/blob/33ef2f747f5cd794018ece3eda4d3908c869ba80/setup.py#L31-L32
In addition, would you be open to including the AWS Auth features as a package extra rather than being included in the core lib (happy to put in a PR). That way the core functionality of this library can depend on as little as possible.
We'd like to use this SDK, but with the current requirements it has pinned it's not possible and we need to revert to using requests.
The text was updated successfully, but these errors were encountered: