RIG v2.0.0-beta.1 Release Notes

Release Date: 2018-06-21 // almost 6 years ago
  • โž• Added

    • Amazon Kinesis integration. #27
    • ๐Ÿ”Š Use lazy logger calls for debug logs.
    • Format (most files) using Elixir 1.6 formatter.
    • โž• Add new endpoint POST /messages for sending messages (=> Kafka is no longer a hard dependency).
    • โž• Add a dedicated developer guide.
    • ๐Ÿš€ Release configuration in rel/config.exs and custom vm.args (based on what distillery is using). #29
    • ๐Ÿ”ง Production configuration for peerage to use DNS discovery. #29
    • Module for auto-discovery, using Peerage library. #29
    • ๐Ÿš€ Kubernetes deployment configuration file. #29
    • โœ… Smoke tests setup and test cases for API Proxy and Kafka + Phoenix messaging. #42
    • Kafka consumer ready check utility function. #42
    • List of all environment variables possible to set in guides/operator-guide.md. #36
    • ๐ŸŒฒ Possibility to set logging level with env var LOG_LEVEL. #49
    • ๐Ÿณ Variations of Dockerfiles - basic version and AWS version. #44
    • ๐Ÿš€ Helm deployment chart. #59
    • Proxy is now able to do request header transformations. #76

    ๐Ÿ”„ Changed

    • Endpoint for terminating a session no longer contains user id in path.
    • Convert to umbrella project layout.
    • ๐Ÿ“š Move documentation from doc/ to guides/ as the former is the default for ex_doc output.
    • ๐ŸŒฒ Revised request logging (currently Kafka and console as backends).
    • โฑ Disable WebSocket timeout. #58
    • ๐Ÿš€ Dockerfile to use custom vm.args file & removed mix release.init step. #29

    ๐Ÿ›  Fixed

    • ๐Ÿ‘‰ Make presence channel respect JWT_USER_FIELD setting (currently hardcoded to "username").
    • Set proper environment variable for Phoenix server INBOUND_PORT. #38
    • Set proper environment variable for Phoenix server API_PORT. #38
    • ๐Ÿ›  Channels example fixed to be compatible with version 2.0.0. #40
    • ๐Ÿ‘‰ User defined query auth values are no longer overridden by JWT auth type.
    • ๐Ÿ– Handle content-type correctly. #61
    • More strict regex match for routes in proxy. #76
    • Downcased response headers to avoid duplicates in proxy. #76