Client package ServiceName literal definitions are not necessarily up-to-date

[jvtm]

Client package ServiceName literal definitions are not necessarily up-to-date

[vemel]

Thank you for the bug report.

It looks like the only proper solution would be to define your own ServiceName literal with the services you use:

ServiceName = Literal["ec2", "s3", "sns"]

class AWSAccess:
    def __init__(self):
        # Some common setup like logging, access rights, etc here.
        # This is a stripped down version for pointing out boto3-stubs related bug.
        pass

    @staticmethod
    def client(service: ServiceName, **kwargs):
        return boto3.client(service, **kwargs)

    @cached_property
    def s3(self) -> S3Client:
        return self.client("s3")

Or, I can regenerate all packages whenever new services are added or removed.

Let me know what you think.

[vemel]

ServiceName and ResourceServiceName up-to-date literals are now included in mypy-boto3 package:

# pip install mypy-boto3
 
from mypy_boto3.literals import ServiceName, ResourceServiceName

@jvtm I released mypy-boto3 1.28.83.post1 version with this change. Please let me know if you are satisfied with this solution.

Usage example can be found here: https://pypi.org/project/mypy-boto3/