[RFC] zabbix: refactor packaging #28238
Draft
+343
−144
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
📦 Package Details
Maintainer: @danielfdickinson
Description:
This changeset will likely need discussion, so creating this draft PR as a Request for Comments.
The first two commits are from #28041 , which is not yet merged.
The third commit is just a simple version bump.
The fourth commit is where the action is (EDIT: and is now v3 of the refactor)
We enable a number of previously disabled features, and in order to
avoid an explosion of 'flavours' of Zabbix, we refactor the packaging
as follows:
All tiny variants omit SSL and have only the base functionality for
the binary. In addition the proxy tiny variant is built against SQLite
as the database.
Small version also omit SSH and only have base functionality for the
binary, but use PostgreSQL or MariaDB for the database.
SSL flavour of OpenSSL vs. GnuTLS is now a configuration option, with
OpenSSL as the default.
When building against GnuTLS the agentd and server full versions have
the following notes:
The full server version uses OpenSSL version of Net-SNMP and the
default SSL backend for cURL on OpenWrt.
Both SSL versions use OpenLDAP from OpenWrt.
Default database for the servers and frontends remains PostgresQL.
The 'extra-auth' frontend has the PHP modules necessary to do LDAP as
well as SAML and MFA.
🧪 Run Testing Details
Only compile-tested so far - this is an RFC, not for merging, yet.
✅ Formalities