Skip to content

docs(idempotency): fix register_lambda_context order #1747

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Nov 24, 2022
Merged

docs(idempotency): fix register_lambda_context order #1747

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/utilities/idempotency.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -136,7 +136,7 @@ When using `idempotent_function`, you must tell us which keyword parameter in yo

This example also demonstrates how you can integrate with [Batch utility](batch.md), so you can process each record in an idempotent manner.

```python hl_lines="4-5 16 21 29"
```python hl_lines="4-5 16 21 30"
from aws_lambda_powertools.utilities.batch import (BatchProcessor, EventType,
batch_processor)
from aws_lambda_powertools.utilities.data_classes.sqs_event import SQSRecord
Expand Down Expand Up @@ -164,9 +164,9 @@ When using `idempotent_function`, you must tell us which keyword parameter in yo

@batch_processor(record_handler=record_handler, processor=processor)
def lambda_handler(event, context):
config.register_lambda_context(context) # see Lambda timeouts section
# `data` parameter must be called as a keyword argument to work
dummy("hello", "universe", data="test")
config.register_lambda_context(context) # see Lambda timeouts section
return processor.response()
```

Expand Down