[FEAT]: Cleanup expired credentials / attestations based on TTL configured for the attestation.

[dileepbapat]

What is the feature request for?

Registry Core

What problem/inconvenience (if any) will this feature solve?

In addition to certificate validity registry custodian can decide to set TTL on verifiable credentials after which sunbird-rc would clear attestations.

TTL (in hour) Per attestation type 0 - do not store attestation (need to evaluate async cases) [n] - store until n hours, any request after that should get attested / pulled again from credential source -1 - can store indefinitely or until cred expires or owning entity exists.

Describe the feature clearly.

Add a new command that does ....

[Sreejit-K]

Discussion on Jun 6 :

• Do the cleanup when ever some try to create a credential
• And also provide them with an API to cleanup when someone want to do a force clean up

Discussion on Jun 10 :

Attestation flow changes :

• Attestation policies with credential template and without credential template
• with credential template :
  1. Expiry date defined
  2. Expiry date is not defined in the credential

Loop through all the attestations and check for credentails with current date expiry time and do a soft or hard delete

• Add New Status named "EXPIRED" in the attestation flow by giving an expiryDate.

What do you mean by cleanUp? Make it configurable. We have to deep dive into the current flow and figure out where to add this env