Skip to content
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.

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

feat(lambda): add isIterator prop #569

Merged
merged 1 commit into from
Sep 9, 2024

Conversation

echeung-amzn
Copy link
Member

We've received feedback that the default IteratorAge widget is largely useless for any Lambda function that isn't actually a stream handler. Function doesn't provide a way to really tell if that's the case, so we ended up with an explicit prop.

We default to true for backwards compat.


By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license

We've received feedback that the default IteratorAge widget is largely useless for any
Lambda function that isn't actually a stream handler. Function doesn't provide a way to really
tell if that's the case, so we ended up with an explicit prop.

We default to true for backwards compat.
Comment on lines +510 to +512
throw new Error(
"addMaxIteratorAgeAlarm is not applicable if isIterator is not true",
);
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I feel I've asked this before, so sorry in advance if i have

Can we use Annotations here? Having the scope included (via Annotations.error(...)) really helps folks find where in their app this is being thrown

@mergify mergify bot merged commit b0cc9b3 into cdklabs:main Sep 9, 2024
11 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants