Tenant Agent Settings

[esune]

This is to support finer-grained tuning of each tenant: the objective is to make tenants as independent as possible when setting-up and maintaining their instance.

Settings that will need to be configurable independently by each tenant:

• Writeable Ledger:
  • Currently the main agent instance (agency) MUST select a writeable ledger using the configuration file and/or the relevant environment variables/startup parameters. This may be used as default setting, but it might be best to not need a pre-selection, if possible.
  • The Traction tenant should be able to select which ledger to write to, and pick an endorser accordingly (or contextually, UX is yet to be explored and defined)
• Agent lifecycle configuration flags:
  • ACAPY_LOG_LEVEL
  • ACAPY_INVITE_PUBLIC
  • ACAPY_PUBLIC_INVITES
  • ACAPY_AUTO_ACCEPT_INVITES
  • ACAPY_AUTO_ACCEPT_REQUESTS
  • ACAPY_AUTO_PING_CONNECTION
  • ACAPY_MONITOR_PING
  • ACAPY_AUTO_RESPOND_MESSAGES
  • ACAPY_AUTO_RESPOND_CREDENTIAL_OFFER
  • ACAPY_AUTO_RESPOND_CREDENTIAL_REQUEST
  • ACAPY_AUTO_VERIFY_PRESENTATION
  • ACAPY_NOTIFY_REVOCATION
  • ACAPY_AUTO_REQUEST_ENDORSEMENT
  • ACAPY_AUTO_WRITE_TRANSACTIONS
  • ACAPY_CREATE_REVOCATION_TRANSACTIONS

Note: thera are several other settings that might be useful to expose, these are a subset base on use-cases at the time of writing.

c.c.: @WadeBarnes

[esune]

Related/blocking issue logged on ACA-Py's repo: openwallet-foundation/acapy#2209

[esune]

Moving to blocked: will close once the related PR is merged in ACA-Py

[swcurran]

Shouldn’t this still be open, since it isn’t working in traction?