feat(parser): Add S3 Object Lambda Event

[ran-isenberg]

implements #361
also added missing imports in init file

[heitorlessa]

Looks great! One minor typo in the docs and I can merge it.

Note to self

For 2.0, I'd love to see how we can reuse data structure between Data classes and Parser. The only three key differences in here are:

1. Parser needs to use multi-inheritance (BaseModel, plus what's already defined)
2. Parser has some pydantic types that are more explicit so ^ could help
3. Data classes use @property to provide per attribute docs, so maybe there's a native way of doing this, so we could reuse code with Parser

Atm, these are the biggest raw code albeit small contributors to the package size (w/o deps)

4.0K	aws_lambda_powertools/utilities/__init__.py
348K	aws_lambda_powertools/utilities/data_classes
192K	aws_lambda_powertools/utilities/parser
108K	aws_lambda_powertools/utilities/parameters
 96K	aws_lambda_powertools/utilities/idempotency
 48K	aws_lambda_powertools/utilities/validation
 44K	aws_lambda_powertools/utilities/batch
 40K	aws_lambda_powertools/utilities/typing

[heitorlessa]

Suggested change

	| **S3ObjectLambdaEvent** | Lambda Event Source payload for Amazon S3 Object Access |
	| **S3ObjectLambdaEvent** | Lambda Event Source payload for Amazon S3 Object Lambda |

[ran-isenberg]

thx! pushed the code fix

[ran-isenberg]

@heitorlessa BTW, more key differences between parser and validator are:

1. We can use Literal types - i thought of using them in this PR but the documentation wasnt clear 100%.
2. We can add validators and root validator. in this case for instance, the userName exists only in some cases - i could add that check to the schema.

[heitorlessa]

Oh I know about the added value of Parser, and Literal types are part of point 1 ;) That note to myself is to remember what a base class for both could look like.

…

On Mon, 29 Mar 2021 at 18:48, Ran Isenberg ***@***.***> wrote: ***@***.**** commented on this pull request. ------------------------------ In docs/utilities/parser.md <#362 (comment)> : > -**SqsModel** | Lambda Event Source payload for Amazon SQS -**AlbModel** | Lambda Event Source payload for Amazon Application Load Balancer -**CloudwatchLogsModel** | Lambda Event Source payload for Amazon CloudWatch Logs -**S3Model** | Lambda Event Source payload for Amazon S3 -**KinesisDataStreamModel** | Lambda Event Source payload for Amazon Kinesis Data Streams -**SesModel** | Lambda Event Source payload for Amazon Simple Email Service -**SnsModel** | Lambda Event Source payload for Amazon Simple Notification Service +| Model name | Description | +| -------------------------- | ------------------------------------------------------------------ | +| **DynamoDBStreamModel** | Lambda Event Source payload for Amazon DynamoDB Streams | +| **EventBridgeModel** | Lambda Event Source payload for Amazon EventBridge | +| **SqsModel** | Lambda Event Source payload for Amazon SQS | +| **AlbModel** | Lambda Event Source payload for Amazon Application Load Balancer | +| **CloudwatchLogsModel** | Lambda Event Source payload for Amazon CloudWatch Logs | +| **S3Model** | Lambda Event Source payload for Amazon S3 | +| **S3ObjectLambdaEvent** | Lambda Event Source payload for Amazon S3 Object Access | @heitorlessa <https://github.com/heitorlessa> BTW, more key differences between parser and validator are: 1. We can use Literal types - i thought of using them in this PR but the documentation wasnt clear 100%. 2. We can add validators and root validator. in this case for instance, the userName exists only in some cases - i could add that check to the schema. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#362 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAZPQBDELS4TKG76TCFM6HTTGCVO3ANCNFSM4ZZL5R3A> .

[heitorlessa]

Thank you once again! Merging now