mirror of
https://github.com/Icinga/icingaweb2-module-businessprocess.git
synced 2026-02-04 01:09:25 -05:00
doc/changelog: add a changelog
This commit is contained in:
parent
98bd02c164
commit
892780de96
3 changed files with 39 additions and 1 deletions
|
|
@ -47,4 +47,5 @@ Documentation
|
|||
|
||||
### The Project
|
||||
* [Project History](doc/81-History.md)
|
||||
* [Changelog](doc/82-Changelog.md)
|
||||
* [Contributing](doc/84-Contributing.md)
|
||||
|
|
|
|||
38
doc/82-Changelog.md
Normal file
38
doc/82-Changelog.md
Normal file
|
|
@ -0,0 +1,38 @@
|
|||
<a id="Changelog"></a>Changelog
|
||||
===============================
|
||||
|
||||
2.1.0
|
||||
-----
|
||||
|
||||
### Fixed issues and related features
|
||||
* You can find issues and feature requests related to this release on our
|
||||
[roadmap](https://github.com/Icinga/icingaweb2-module-businessprocess/milestone/4?closed=1)
|
||||
|
||||
### Usability and visualization
|
||||
* Missing nodes are now shown in a generic error notice
|
||||
* `Unbound nodes` (nodes not being shown at top level and not in use as a sub
|
||||
node) are now reachable through a fake node
|
||||
* A bug with the Chrome browser showing messed up checkboxes has been fixed
|
||||
|
||||
### State calculation
|
||||
* Missing nodes are now considered being `UNKNOWN` (or `UNREACHABLE` when
|
||||
being a host node). The former behaviour comes from Icinga 1.x, as a reload
|
||||
there had the potential to trigger false alarms. This is no longer an issue
|
||||
with Icinga 2.x, allowing us to be strict once again when it goes to missing
|
||||
nodes
|
||||
* Linking nodes from other process configuration files (still an undocumented
|
||||
feature) has been broken shortly before 2.0.0, this has now been fixed
|
||||
|
||||
### Permissions
|
||||
* Permissions have not been enforced as they should have been in 2.0.0, some
|
||||
links and operations have been accessible to roles that haven't been granted
|
||||
such. This has now been fixed
|
||||
* While we allow for granular permissions that can be persisted in every process
|
||||
configuration file (still an undocumented feature), there is now also a pretty
|
||||
simple but effective way of restricting access to your business processes based
|
||||
on process name prefixes.
|
||||
|
||||
2.0.0
|
||||
-----
|
||||
|
||||
* First officially stable version
|
||||
|
|
@ -495,7 +495,6 @@ class BpConfig
|
|||
{
|
||||
if ($name === '__unbound__') {
|
||||
return $this->getUnboundBaseNode();
|
||||
|
||||
}
|
||||
|
||||
if (array_key_exists($name, $this->nodes)) {
|
||||
|
|
|
|||
Loading…
Reference in a new issue