Open dlongley opened 2 years ago
Unique indexes on service type will need adjustment to support this and sharding.
Consider making this additive by allowing service objects to be created with an agent, if requested, the ID (DID) of which can be fetched from the service object config. The existing service agent (to be distinguished from a service object agent) can continue to be used to perform meter interactions, uninterrupted by this new feature.
The provisioning process would be:
agent
field of the service object config.agent
field value could be used as the controller
(delegatee) for any zcaps to be given to the service object that it needs to perform its duties.Removing priority label from this because the value of adding this feature is in question. More debate is needed before proceeding with implementation or with closing this issue (either option is possible).
Add option to create per-service-object-instance agents. This would allow HSM-bound zcap keys to specific service objects such that zcaps could be assigned them.