Releases: JeremieRodon/lambda-appsync
Releases · JeremieRodon/lambda-appsync
v0.9.0
Added
- Tracing support: New
tracingfeature flag enables tracing/tracing-subscriber integration as an alternative to env_logger - Configurable logging initialization: New
log_init = function_namemacro parameter allows custom log initialization functions instead of relying on defaults - Event logging control: New
event_logging = boolmacro parameter controls whether Lambda event payloads are logged (defaults tofalsefor better security) - Structured JSON logging by default when tracing is enabled
#[tracing::instrument]attributes on generated handler functions with request ID and operation name in trace spans- Signature validation for the
hookoption with clear error messages for invalid function signatures
Changed
- Breaking: Event payload logging is now disabled by default for security reasons (can be re-enabled with
event_logging = true) - When Lambda event payloads logging is enabled, Lambda event payloads are now logged at
debuglevel instead ofinfo env_loggeris now an optional feature (still enabled by default for backward compatibility)- Independent
logfeature flag controls log statement generation in generated code
Fixed
- Generated
mainandfunction_handlernow use fully qualified::core::result::Resultinstead ofResult, preventing compilation failures when users override the Result type - Request hook trybuild test was not actually testing anything
- Release CI could fail tests but still proceed with publishing
Full Changelog: v0.8.0...v0.9.0