On Jan 31, 2018, at 09:28, Jan Jancar <jo...@neuromancer.sk> wrote: > Plugin configuration is done through the Mailman configuration and those > are read-only through the REST interface. However a plugin might supply > it's own REST endpoints for example for per-list setup/configuration.
Yep; configuration options are read-only through REST because they are specified in the mailman.cfg file. You wouldn’t want to (and probably even can’t) allow REST clients to change things that aren’t kept in the database. On Jan 31, 2018, at 15:03, holger <hol...@merlinux.eu> wrote: > sounds good. Is it also possible to hook into the standard mm3 configuration, > for adding a per-list configuration item that can then be processed by > plugin code? Per-list configurations are maintained in the database, configuration files (e.g. mailman.cfg) configure site-wide static settings. That’s because lists are dynamic; they can be created, deleted, and modified. But your plugin should be able to create its own tables and cross reference the mailing list tables (via the SQLAlchemy ORM). Static configurations can be added to a [plugins.autocrypt] section, or better a separate autocrypt.cfg file, much like the way we separate out the postfix.cfg settings. Cheers, -Barry
signature.asc
Description: Message signed with OpenPGP
_______________________________________________ Mailman-Developers mailing list Mailman-Developers@python.org https://mail.python.org/mailman/listinfo/mailman-developers Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-developers%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-developers/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
