Hello James community,
Today we have the webadmin-cli (which is sadly not actively developed)
in its own maven module, consisting of picocli code for the CLI
interaction calling a feign + jackson API to act on the remote WebAdmin API.
Linagora plans to set up a SaaS offer of a re-packaging of James (we
call it TMail). We will implement a third party Java service that will
call weAdmin endpoints in order to configure TMail/James according to
the SaaS subscriptions.
As such we will need a programmatic way to create users, domains,
quotas, etc...
We would like to reuse existing code, but without pulling the unneeded
picocli dependency.
Thus we propose to set up a new maven module, `webadmin-http-client` for
hosting this feign+jackson library, which `webadmin-cli` can depend on.
As part of this effort, we will also contribute the API calls for
configuring quotas at the domain level.
Would this seem like a good move to you?
Best regards,
Benoit Tellier
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
