v1.0.4

• When forwarding recordings from one Kerberos Vault to another Kerberos Vault, it might happen that the file was uploaded to the designated storage provider but silently fail. This can cause the recording being labeled as "not" forward, and will trigger the upload again. When setting specific policies on the storage provider (e.g. google cloud storage), the storage provider might refuse the new upload, which will result in an endless loop. The latter was fixed, but it still created duplicate messages, as the integration was still being executed. Now when we have a duplicate file, we should stop, and create no additional messages.
• Have the possibility to define multiple concurrent queues. This means that on uploading of a recording we will create multiple messages in various queues at the same time.
• Docker Hub image repository was changed we moved to uugai/vault.