icingadb-web/test/php/Lib/PerfdataSetWithPublicData.php

<?php

/* Icinga DB Web | (c) 2023 Icinga GmbH | GPLv2+ */

namespace Tests\Icinga\Module\Icingadb\Lib;

use Icinga\Module\Icingadb\Util\PerfDataSet;

class PerfdataSetWithPublicData extends PerfdataSet
{
    public $perfdata = [];
}
Introduce monitoring's perfdata tests here 2023-01-17 11:44:08 -05:00			`<?php`

Upgrade license from GPLv2 to GPLv2+ 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. 2025-11-21 07:31:24 -05:00			`/* Icinga DB Web \| (c) 2023 Icinga GmbH \| GPLv2+ */`
Introduce monitoring's perfdata tests here 2023-01-17 11:44:08 -05:00
			`namespace Tests\Icinga\Module\Icingadb\Lib;`

			`use Icinga\Module\Icingadb\Util\PerfDataSet;`

			`class PerfdataSetWithPublicData extends PerfdataSet`
			`{`
			`public $perfdata = [];`
			`}`