Default S3 behavior - "--simulation" feature

[dirkpetersen]

I think it is a good idea to make the config of S3 providers optional to allow for people who just want to use the froster index feature. Should this not default to (Y/n) ?:

[?] Do you want to configure S3 providers? (y/N):

but then is the question what we do with folks who already have configured a [default] aws profile with credentials

if i run froster archive it get this, even if there is a default AWS profile

froster archive /home
Error: Invalid credentials.
  Profile: None
  Provider: AWS
  Endpoint: None

this should have an error message saying something like " please run froster config and make sure you activate/configure S3 profiles."

[macheitor]

The default answer is "y/N" so if the user press enter it won't configure any S3 provider. This is what you are expecting. Or am I mistaken?

Regarding default credentials, the AWS still needs to be configured so the user selects the bucket, the archiving dir, etc. While configuring AWS provider user should select the "default" profile from the list of available aws profiles if those credentials ara valid. Did you do that in your example?

[macheitor]

I see, You are getting this because AWS is the fallback provider in case nothing is configured. If nothing is configured i'll set the provider to None. I'll also change the message so the user knows that he has to configure a provider

[dirkpetersen]

The default answer is "y/N" so if the user press enter it won't configure any S3 provider. This is what you are expecting. Or am I mistaken?

Regarding default credentials, the AWS still needs to be configured so the user selects the bucket, the archiving dir, etc. While configuring AWS provider user should select the "default" profile from the list of available aws profiles if those credentials ara valid. Did you do that in your example?

In more than 50% of the cases i would assume the user would want to configure a profile ..... now we have seen that people want to sometimes try froster out without actually uploading to cloud ...... but for that to be effective you would have to allow the user to get all the way up to run froster archive, then pick a hotspot to experience that functionality and then tell them they have not configured a profile yet.... but how froster is currently working I would default to configure a profile

[macheitor]

Froster allows configuration, indexing, and updates to be performed without credentials.
Other commands need credentials for Rclone to run.

I suggest implementing a "--simulation" feature to allow users to use all Froster features without interacting with a real S3 server. However, this feature will be implemented in future Froster implementations.
I'll change the title of this ticket so this suggestion does not get lost