Releases: Templum/rabbitmq-connector
Releasing reworked connector 1.0.0
Hello,
this version brings a breaking change compared to the v0.x.x versions. Instead of automatically having the exchange + queues generated, you can now bring your existing exchanges. This is done by providing a path to the exchange declartion, which has the following format:
# Name of the exchange
- name: Exchange_Name # Required
topics: [Foo, Bar] # Required
# Do we need to declare the exchange ? If it already exists it verifies that the exchange matches the configuration
declare: true # Default: false
# Either direct or topic
type: "direct" # Default: "direct"
# Persistence of Exchange between Rabbit MQ Server restarts
durable: false # Default: false
# Auto Delete Exchange once all consumers are gone
auto-deleted: false # Default: false
An Example configuration that is used for integration tests can be found here.
Changelog:
- Implementation of #33, which is a breaking change compared to 0.x.x
- Implementation of #77
- Golang update to
1.16
- Alpine update to
3.13.2
Support for OpenFaaS Multi Namespace
Update Go Version 1.13 -> 1.15
This release brings the following updates:
- Alpine Version
3.11
=>3.13.1
- Go
1.13
=>1.15.7
Further corrected documentation to highlight that Queue Names are generated with respect to the topic name. Additionally, this is the first release that is built using the GitHub-actions pipeline, which now also publishes to the Github Container Registry.
Minor Fix
This release includes #58, which will take the defined Content-Type
& Content-Encoding
from the original Rabbit MQ Message and leverage it when making the request to OpenFaaS.
If you did not have any issues previously in regards to parsing the request content within a lambda, then probably this release won't have any impact on you.
Minor Fixes
This release includes the following things:
- Updated Alpine Version 3.10 -> 3.11
- Added Env
INSECURE_SKIP_VERIFY
: Allows to skip verification of HTTP Cert for Communication Connector <=> OpenFaaS. - Fix for Namespace Scraping when Backend does not support Namespaces (#50)
Swapped OpenFaaS SDK
This minor release contains some changes to the internal architecture.
- Removed the official OpenFaaS SDK and replaced it by a custom implementation that is tailored to the needs of this connector.
- Extended logging when an unexpected Topic is received, usually this indicates that the topic is in the wrong mode.
- Updated some packages
- Updated from go 1.10 => 1.13
- Updated base image from alpine 3.8 => 3.10
The swapping of the SDK should allow for better information, in case the communication with OpenFaaS was not setup correctly. E.g. wrong/missing Auth Credentials (Common issue)
Bugfix for #26
This release includes a bugfix for issue #26.
The Exchange is now configured as Direct
. Further, the connector will now create a dedicated Queue per Topic Key.
Initial Release
This version allows a basic setup with Rabbit MQ and OpenFaaS.
- Messages received will be used to invoke a function on OpenFaaS, if there is a function listening on that event
- Be aware that the connector will drop messages if there is no lambda (yet) listening for them.