Releases: eiffel-community/eiffel-intelligence
Releases · eiffel-community/eiffel-intelligence
0.0.8
- Added new endpoints for checking status and security
- Added endpoints for getting rules and events templates
- pom updated- changing some dependenvy version
- Removed checking by userName from getSubscription method
- Freestyle query is performed only on aggregated_objects collection
- Fix information endpoint
Implemented Authorization and other changes
Released changes :
- Added LDAP authorization configuration
- Added authorization endpoints
- Added MongoDB session handling
- Added user authorized subscription operations
- Improved internal composition handling
- Improved SubscriptionRepeatHandlerDB cleanup
- Stepped Spring Boot version
- Stepped Lombok version
Implemented repeat flag in subscription and some changes
Released changes :
• Added rules to create an aggregated object for each received event.
• Make tests to run in parallel
• Functionality for handling repeat flag when processing subscriptions
• Updated subsceriptionTemplate json file with new and latest format
Refactoring tests, add more tests
Refactoring flow tests
Add tests for subscription handler
Release with several new features and improvements
New features and improvements:
- Make ERQueryService operations safe
- Aggregation of historical events when a new start event is consumed
- Updates on some Extraction rules
- Favicon added
- REST_POST_JENKINS multivalue functionality added
- Subscription multikey post form and raw json body support added
- Subscription Validation for Mail added
- Free style query on aggregated object Rest Entrypoint added.
- Subscriptions handling of multiple Mail receivers added.
- Some general improvements and fixes.
AMQP SSL/TLS Protocol support added.
AMQP SSL/TLS Protocol support added.
Deployable in Tomcat
Made it deployable as a web app in a Tomcat server.
First release
Simple aggregation of information from different Eiffel events. Documentation to come next weeks.
Possibility to subscribe for certain contents fulfilled in the aggregated object and require REST POST or email notification when subscription is fulfilled.