You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 0418829
Browse filesBrowse the repository at this point in the historyBrowse files
fix(lambda): stop rejecting values AWS documents as valid
A comprehensive validation pass against the API reference found the previous
commit's blanket "no empty optional strings" rule was wrong. Several Lambda
parameters document an empty string as meaningful, and their patterns say so:
KMSKeyArn, SourceKMSKeyArn, and DeadLetterConfig.TargetArn all carry
`(arn:...)|()`, whose trailing alternative matches the empty string, and the
on-success/on-failure destinations document `Minimum length of 0` with a
pattern beginning `$|`. For each, empty is how the setting is cleared.
The rule is now opt-in rather than opt-out: only the five fields feeding a
truthiness-based cross-field check reject an empty value. That removes 47
constraints and leaves the ones that were actually reported.
Also from the same pass:
- Supplying an image URI no longer demands an explicit `packageType`. That
subBlock is advanced with no default, so requiring it produced a 400 naming
a control the user cannot see; the operation derives Image from the code
source instead, and only an explicit Zip alongside an image is rejected.
- `fileSystemConfigs` was the one projection without a null guard, so an
omitted field vanished from the block output rather than reading null.
- An absent function URL now maps to null instead of an empty string a
workflow could build a request against.
- GetFunction reports `tagsError`, so a partial tag-read failure is
distinguishable from a function with no tags, and marks `configuration`
nullable to match what the operation returns.
- Event source mappings report `selfManagedKafkaBootstrapServers`, which
could be set but never read back.
- TagResource rejects an empty tag map instead of reporting "0 tags applied".
0 commit comments