You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add the ability to "auto-delete" credentials and proof exchange records. using the global configurations and method-level parameters. That might help prevent the PII data and help with storage optimization.
The text was updated successfully, but these errors were encountered:
Yes I agree, that's a good one, and could be done immediately after emitting the error/success event. However this won't help for exchanges that are never completed.
You can quite easily build this on top of credo. Once you receive the completed/error event you delete the record. You can also run a cron script that deletes all records older than e.g. an hour every x minutes/hours/days.
We're working on some new models for storage that would also make it easy to find records that were created e.g. more than one hour ago.
I was considering a flag-based implementation, similar to the preserve-exchange-record approach in ACA-Py. I agree that an event-driven implementation could be a more straightforward way to achieve this. Do you plan to incorporate a flag-based approach with global parameters in the future?
Add the ability to "auto-delete" credentials and proof exchange records. using the global configurations and method-level parameters. That might help prevent the PII data and help with storage optimization.
The text was updated successfully, but these errors were encountered: