What's new?
This is a patch release, focused on bug fixes. It addresses many little issues related to the Configuration Basket (available since v1.6.0), brings back our loop detection and improves the Blacklisting feature. It is now possible to grant a read-only view for Services, allowing one to see where they originated. A new REST API endpoint has been introduced for those who want to deal with Service Apply Rules.
Looping Louie is Looping again!
Fixed issues
- You can find issues and feature requests related to this release on our
roadmap
User Interface
- FIX: restoring a basket fails when there is only one configured DB (#1716)
- FIX: creating a new Basket with a "Custom Selection" failed with an error (#1733)
- FIX: some new reserved keywords are now escaped correctly (#1765)
- FIX: correctly render NOT used in apply rules (fixes #1777)
- FIX: Activity Log used to ignore Host filters (#1613)
- FIX: Basket failed to restore depending on PHP version (#1782)
- FIX: Loop detection works again (#1631)
- FIX: Snapshots for Baskets with Dependencies are now possible (#1739)
- FIX: Commands snapshots now carry fields in your Basket (#1747)
- FIX: Cloning services from one Set to another one no longer fails (#1758)
- FIX: Blacklisting a Service from a Set on a Host Template is now possible (#1707)
- FIX: Services from a Set assigned to a single Host can be blacklisted (#1616)
- FEATURE: Add TimePeriod support to Configuration Baskets (#1735)
- FEATURE: RO users could want to see where a configured service originated (#1785)
- FEATURE: introduce director/serviceapplyrules REST API endpoint (#1755)
REST API
- FIX: Self Service API now ships optional Service User parameter (#1297)
DB Schema
- FIX: it wasn't possible to use the same custom var in multiple notification
definitions on PostgreSQL (#1762)
Icinga Configuration
- FIX: escape newly introduced Icinga 2 keywords (#1765)