No error message if tails server is down
When creating a credential definition for a revocable credential, AcaPy does not throw any error even if the tails server is down and the tails file can not be stored on the tails server.
Only the holder raises an error as soon as it tries to generate a presentation.
I would have expected an error to be returned by POST /credential-definitions or at least via the webhook /topic/revocation_registry/. Also in the logs of AcaPy I did not see any message indicating that there is an issue writing a file to the tails server.
Discussion in AcaPug Call 3rd of May 2022:
Idea 1: It would be nice if the tails file is uploaded first and then written to the ledger
- tails server is currently verifying that the tails file is already mentioned in a transaction on the ledger before it accepts tails files -> this check is in place to ensure that only tails files are being uploaded
- still, it would be possible to rethink the tails server to make it possible to first upload tails files and then write them to the ledger
Idea 2: Should consider an alternative revocation mechanism that is not using tail files at all
Idea 3: Only set the RevReg status to active once the tails file has been uploaded successfully