Releases: kalaspuff/tomodachi
Releases · kalaspuff/tomodachi
0.14.1
0.14.0
- Added the possibility of specifying
message_protocol
for AMQP / SNS+SQS enveloping per function, so that it's possible to use both (for example) raw data and enveloped data within the same function without having to build fallback enveloping functionality. - Added documentation for
@tomodachi.decorator
, describing how to easily write decorators to use with service invoker functions. - Added
ignore_logging
keyword argument to HTTP invoker decorator, which may ignore access logging for either specific status codes or everything (except500
statuses). [@justcallmelarry] - New function
tomodachi.get_service()
ortomodachi.get_service(service_name)
available to get the service instance object from wherever in the running service, much likeasyncio.get_event_loop()
. - Updated examples.
- Fixes issue which caused
aiohttp
FileResponse
responses to raise an internal exception. - Added support for
aiohttp
3.4.x.
0.13.7
0.13.6
0.13.5
- Fixes an issue which caused HTTP invoker functions to be accessible before the bootstrapper function
_start_service()
had been completed. Now_start_service()
is called first, followed by activation of the invoker functions (@http
,@schedule
,@aws_sns_sqs
,@amqp
, etc.) and then lastly the_started_service()
function will be called, announcing that the service is now up and running.
0.13.4
0.13.3
0.13.2
0.13.1
0.13.0
- Restructured base message protocols for both JSON and ProtoBuf. JSON protocol is now called
tomodachi-json-base--1.0.0
(earlierjson_base-wip
) and the ProtoBuf protocol is now referred to astomodachi-protobuf-base--1.0.0
. Updated proto files are not compatible with earlier protocolprotobuf_base-wip
.