Hello community!
When I am using keydb-server --db-s3-object s3://<my-bucket>, server starts successfully and writes backup to file named "-" in my bucket. Eventually after restart it fails with some decryption issue since it can't decode "-" file.
On the other hand, when I am specifying specific file name with keydb-server --db-s3-object s3://<my-bucket>/dump.rdb, it says "could not access s3 bucket" (if I have no file in S3 beforehand).
If I create the file before starting server with previous command, it works fine.
Isn't it expected that keydb should write initial file to S3 as at the first start there is no dump file for me yet? If without file name specification, it successfully creates file called "-", then it has such ability, but there is some bug in existence check?
Hello community! When I am using
keydb-server --db-s3-object s3://<my-bucket>, server starts successfully and writes backup to file named "-" in my bucket. Eventually after restart it fails with some decryption issue since it can't decode "-" file. On the other hand, when I am specifying specific file name withkeydb-server --db-s3-object s3://<my-bucket>/dump.rdb, it says "could not access s3 bucket" (if I have no file in S3 beforehand). If I create the file before starting server with previous command, it works fine.Isn't it expected that keydb should write initial file to S3 as at the first start there is no dump file for me yet? If without file name specification, it successfully creates file called "-", then it has such ability, but there is some bug in existence check?