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

fix(type-safe-api): ensure lambda function names do not exceed max length #619

Merged
merged 1 commit into from
Oct 30, 2023

Conversation

cogwirrel
Copy link
Member

Truncate the lambda function names for the custom resource to ensure they are below the max length of 64 characters.

Fixes #615

…ngth

Truncate the lambda function names for the custom resource to ensure they are below the max length
of 64 characters.

Fixes #615
@cogwirrel cogwirrel merged commit 8e7b8b5 into mainline Oct 30, 2023
3 checks passed
@cogwirrel cogwirrel deleted the fix/lambda-name-length branch October 30, 2023 03:31
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.

[BUG] (type-safe-api) PrepareSpec function name too long
2 participants