Skip to content

Beta 1.15.2
Compare
Choose a tag to compare
@tmaiaroto tmaiaroto released this 05 Jul 23:17
· 14 commits to master since this release
1.15.2
f888f2a

This patch release includes additional fixes for deploy that include the addition a retry and delay. After creating new IAM roles, it is possible that they are not yet available to be used by a Lambda function. Previously there was a short delay in the deploy command. Now there's a longer delay, but it is done so incrementally in a retry loop/goroutine. This puts a limit on how many times things get retried, but also doesn't wait longer than necessary.

Additionally, an Error field has been added to the CognitoToken struct in the Cognito client service. This allows end user code to handle errors coming back from Cognito. Such cases can arise based on the pool configuration. More work on this service to come, but for now the ability to know there's an issue has been put in place.

1.15.0

SQS triggers have been added by AWS! This release provides a new, easy to use, router for working with them. This release also focused on wrapping up documentation (including SQS router).

  • SQS message router
  • Various fixes to TraceStrategy and Tracer

1.14.0

  • The S3ObjectRouter received a couple of fixes (among them #29)
  • TraceStrategy interface was overhauled making it easier to implement your own trace strategies as well as making it easier for Aegis to run unit tests.
  • More test cases were added and the S3 router has high coverage now (more tests to come for other routers)

1.12.0

  • Moved local HTTP server to Aegis interface; it will eventually handle more than just
    HTTP requests (which mimicks APIGatewayProxyRequest) - this creates a very small breaking
    change, the old router.Gateway() is simply replaced by app.StartServer() where app
    is an instance of Aegis interface
  • Moved test cases accordingly, many of the functions to convert requests/responses
    were simply moved
  • Added StartSingle() which takes an --event flag when running the binary for the
    event and returns a pretty printed result (optional) or error message to the CLI
    (also can flag --pretty for this and --nolog to hide any log output from the app)

1.11.0

  • Added SES integration; configure rules in aegis.yaml and handle with SESRouter handlers
  • Fixed bug when handling with nil Router, it will now return an error explaining that no handleres have been set to handle the event (this can occur if a router was registered, but not added to aegis.Handlers{}, leading to some confusion)
Assets 3
Loading