Mercurial > libervia-backend
view doc/libervia-cli/pubsub_node_affiliations.rst @ 4112:bc60875cb3b8
plugin XEP-0166, XEP-0167, XEP-0234, XEP-0353: call events management to prepare for UI:
- XEP-0166: add `jingle_preflight` and `jingle_preflight_cancel` methods to prepare a
jingle session, principally used by XEP-0353 to create and cancel a session
- XEP-0167: preflight methods implementation, workflow split in more methods/signals to
handle UI and call events (e.g.: retract or reject a call)
- XEP-0234: implementation of preflight methods as they are now mandatory
- XEP-0353: handle various events using the new preflight methods
rel 423
| author | Goffi <goffi@goffi.org> |
|---|---|
| date | Wed, 09 Aug 2023 00:07:37 +0200 |
| parents | c80a0f864b5d |
| children |
line wrap: on
line source
.. _libervia-cli_pubsub_node_affiliations: ======================================================= pubsub/node/affiliations: nodes affiliations management ======================================================= ``affiliations`` is a subcommand handling the affiliations of a node (not to be confused with ``pubsub affiliations`` which handle the affiliations of a PubSub service). get === Retrieve entities affiliated to this node and their role. example ------- Get affiliations of a node:: $ li pubsub node affiliations get -n some_node set === Set affiliation of an entity on a node. Affiliations are specified with ``-a JID AFFILIATION`` argument. Check `XEP-0060 affiliations`_ for allowed values for ``AFFILIATION``. Use ``none`` to remove an affiliation. .. _XEP-0060 affiliations: https://xmpp.org/extensions/xep-0060.html#affiliations example ------- If we have a whitelisted node ``some_whitelisted_node``, we can allow ``louise@example.net`` to publish on it (by setting her role as ``publisher``), and ``pierre@example.net`` to access it (by setting his role as ``member``) using the following command:: $ li pubsub node affiliations set -n some_whitelisted_node -a louise@example.net publisher -a pierre@example.net member