Skip to content

v0.2.3 Fixes & full support for arbitrary responses

Compare
Choose a tag to compare
@FieryCod FieryCod released this 14 Jul 08:13
· 217 commits to master since this release
0.2.3
0f1c701
This commit was signed with the committer’s verified signature.
FieryCod Karol Wójcik
GPG key ID: EB3C36A52A7DE9C1
Learn about vigilant mode.

  • [bb tasks] Add support for passing arguments to commands in -- style.

    Example

    bb stack:invoke --validation-fn '(fn [response] true)'

  • [ci] Run integration tests on all supported GraalVM images

  • [bb tasks] Add experimental support for setting some of HL options via AWS variables. This should ease pain of using HL with AWS vault.

  • [docker] Add fierycod/graalvm-native-image:dev which targets GraalVM CE dev releases :)

  • [docker] Add zip program for CI based deployments where tasks are run in Docker context

  • [bb tasks] Remove clj-kondo from the required commands

  • [holy-lambda] Interceptors should not throw when response is byte encoded

  • [holy-lambda] Don't use -H:+AllowIncompleteClasspath on behalf of user

  • [holy-lambda] Use DISABLE_SIGNAL_HANDLERS="true" in bootstrap file

  • [holy-lambda] Allow users to support arbitrary response if the response is byte encoded. Opens a way to support transit and other content-types.

  • [holy-lambda] Properly parse response. Add support for AWS Step Functions.

  • [holy-lambda] Use config-merge-dir instead of config-output-dir when executing bb native:conf. User should be allowed to specify custom configuration in reflect-config.json, resource-config.json that should not be overriden.

  • [holy-lambda] Add support for sending a base64 encoded images from HL hr/png-image

Assets 2
Loading