Credential record state not updated after revocation

[DaevMithran]

There should be a credential_revoked state for credential records, currently we have to use a seperate api to know the revocation status and the state of credential records remain in credential_issued even after revocation. The update should also reflect in the credential records.

[swcurran]

Agreed. Could you do a PR for this?

That said -- our general philosophy is credential status be kept by the controller with the business logic, and not remain in the ACA-Py secure storage beyond the execution of the issuance protocol. That means both that the secure storage DB size is minimized and reduces security concerns about PII storage as it will only be in one place long term (the business system) and not replicated in the agent secure storage.

[DaevMithran]

Agreed. That's a valid point. As we are supporting revocation in two ways either using cred_ex_id or rev_reg_id. The first approach will work only if the credential record is in the ACA-Py secure storage, So we can change the state of credential record to credential_revoked only when the credential record is in the ACA-Py secure storage.
I'll create a PR for this. Thank you for the response.

[swcurran]

Addressed by #1545