-
Notifications
You must be signed in to change notification settings - Fork 1
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
Throw an error when resulting response is over 4096 bytes #3
Comments
taylorb-syd
added a commit
that referenced
this issue
Feb 15, 2021
Requires testing, merged progress into |
taylorb-syd
added a commit
that referenced
this issue
Feb 15, 2023
* [Issue #18] Changed Whitelist/Blacklist to Allowlist/Blocklist, Refactored Code, Improved Testing Code, Improved README.md grammar * [Issue #3] Introduced logic to check size of response. Refactored decorator exception handling. * [Issue #4] Introduced a function to collapse the output data and used this in the cfnresponse function * [1.2.0rc1] Documentation Pass to improve README.md * [Issue #2] Implemented Unit Tests * [Issue #21] Added the response headers for troubleshooting to the debug log output
taylorb-syd
added a commit
that referenced
this issue
Feb 15, 2023
* [Issue #18] Changed Whitelist/Blacklist to Allowlist/Blocklist, Refactored Code, Improved Testing Code, Improved README.md grammar * [Issue #3] Introduced logic to check size of response. Refactored decorator exception handling. * [Issue #4] Introduced a function to collapse the output data and used this in the cfnresponse function * [1.2.0rc1] Documentation Pass to improve README.md * [Issue #2] Implemented Unit Tests * [Issue #21] Added the response headers for troubleshooting to the debug log output
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
CloudFormation cannot accept objects over 4096 bytes. This will result in a signal failure. We should therefore catch the case when the response exceeds more than 4096 bytes and throw a FAILED event instead.
The text was updated successfully, but these errors were encountered: