Closed ckunki closed 1 year ago
Proposal
BUCKETFS_BUCKET
is unset then BFSC prepends "default" to the path of the URI specified on command line.BUCKETFS_BUCKET
is set to an non-empty string then BFSC prepends this name.BUCKETFS_BUCKET
is set to an empty string then BFSC will not prepend any prefix.Decision: BFSC should use prefer "profiles" over environment variables, compare aws cli.
How about non-public buckets with a read password? Does BFSC need to provide additional support here?
see L3-144, https://docs.exasol.com/db/latest/database_concepts/bucketfs/database_access.htm
As passwords for access to BucketFS in file /exa/etc/EXAConf
are base64-encoded, the initial list of planned featured for BucketFS client (BFSC) included to optionally decode these passwords to make life easier for users.
Besides the PRO-argument
Naive users should neither need to manually base64-decode the passwords nor to find out how to do this on the command line.
a short discussion has shown some counter arguments:
/exa/etc/EXAConf
the user potentially might have remembered the original password without base64-encoding. In this case the user does not need a decoding feature in BFSC./exa/etc/EXAConf
. Nor would this user then actively look for a decoding option of BFSC.
See https://github.com/exasol/bucketfs-python/issues/33
cp
)ls
,cp
,rm
incl. upload and download of directories (potentially with multiple files)cp
supports to leave filename unchanged and omit from target path*
and?
for source URIscp a.txt b.txt bfs:/
mv
command: rejected as not supported by HTTP API