This release is a pre-release and may not be stable for production use.
A thin wrapper around boto3
## features
- intelligent connection caching.
- handles pagination for certain client methods.
- rate limit handling, with exponential backoff.
- multi-account sts:assumerole abstraction.
## Example
# Using wrapper methods:
from botor.aws.sqs import get_queue, get_messages
conn_details = {
'account_number': '111111111111',
'assume_role': 'MyRole',
'session_name': 'MySession',
'region': 'us-east-1'
}
queue = get_queue(queue_name='MyQueue', **conn_details)
messages = get_messages(queue=queue)
# Using the botor class
from botor import Botor
Botor.go('kms.client.list_aliases', **conn_details)
botor = Botor(**conn_details)
botor.call('kms.client.list_aliases')
# directly asking for a boto3 connection:
from botor.aws.sts import boto3_cached_conn
conn = boto3_cached_conn('ec2', **conn_details)
# Over your entire environment:
from botor.decorators import iter_account_region
accounts = ['000000000000', '111111111111']
conn_details = {
'assume_role': 'MyRole',
'session_name': 'MySession',
'conn_type': 'boto3'
}
@iter_account_region('kms', accounts=accounts, regions=['us-east-1'], **conn_details)
def list_keys(conn=None):
return conn.list_keys()['Keys']
Metadata
Release files for botor 0.0.1dev8
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| botor-0.0.1dev8.tar.gz | 11.3 kB | Without provenance | Details for botor-0.0.1dev8.tar.gz |
Release files / botor-0.0.1dev8.tar.gz
| Download URL | botor-0.0.1dev8.tar.gz |
|---|---|
| Size | 11.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e88ff53f34cf6a00495f83233bae37de4ec79780aebb09c54c67bb573472c55e
|
|
BLAKE2b-256 checksum How to use checksums |
2afc1a53f831067789d4152199f9ec1b119af1acb3553c083a1a803464a39455
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for botor 0.0.1dev8
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.