Because assets aren't associated with a Wallet Address like Open Payments resources are, it becomes necessary to add a tenantId to them to determine which tenant that asset belongs to.
[ ] Add required tenantId column to assets table
[ ] Acquire tenantId from request header and pass into asset service logic during graphql requests
Because assets aren't associated with a Wallet Address like Open Payments resources are, it becomes necessary to add a tenantId to them to determine which tenant that asset belongs to.
tenantId
column toassets
tabletenantId
from request header and pass into asset service logic during graphql requeststenantId
to database queries on assetsPrerequisites: