This was easy because only README.md and doc/01-About.md were redacted manually, everything else via:
git ls-files -z |xargs -0 perl -pi -e 's/Icinga GmbH \| GPLv2/Icinga GmbH | GPLv2+/'
This is legal because we have only merged PRs with label:cla/signed or made by Icinga staff:
https://github.com/Icinga/icingadb-web/pulls?page=1&q=is%3Apr+is%3Aclosed+-label%3Acla%2Fsigned+-author%3Anilmerg
This has no risk for us in people distributing their own version under GPLv3 only.
After all, we won't take their patches anyway, unless they sign our CLA.
This is the cleanest solution for having e.g. these in one address space:
* Icinga Web, GPLv2+
* K8s Web, AGPLv3
* Thirdparty, some LGPLv3 and Apache-2.0
Apropos, K8s Web is even v3-licensed on purpose, to have a stronger protection against cloud ops.
- Use these renderers in ObjectHeader and ObjectList class
- Remove now superfluous Host/ServiceList and ListItem classes
- DetailsAction: Change visibility of url setter to public (These are called in controller now)
With recent changes in IPL - ORM [1], utilized relations no longer
perform subquery filters, which is fine since the only designed
difference is that columns from utilized relations are not appended to
the select list. However, this change produces empty results here
because the filter should actually be run in a subquery. We called
utilize() here because we modified the base query to apply the group ID
filters. Now that we're using filters that automatically handle
relations, it's safe to remove the utilize() calls.
[1] https://github.com/Icinga/ipl-orm/pull/44
