multi-profile options disappeared

An earlier version of Froster has this


  --profile aws_profile, -p aws_profile
                        which AWS profile in ~/.aws/ should be used. default="aws"

but the profile option has now disappeared. The older version configuration was treating AWS as the primary (mandatory) provider and was then looping through all other profiles and asking the user if they wanted to configure one of them and read profiles from ~/.aws to obtain the defaults. The only thing that was stored in Froster was the provider name and the bucket name, tier and bucket prefix were treated as global settings, with the option to browse the bucket list we should now have a bucket per profile. Let's assume we have 3 configured 3 profiles, config.ini could look like this:

[USER]
name = Dirk Petersen
email = dirk@moin.me

[SHARED]
is_shared = False
shared_dir =
shared_config_file =

[NIH]
is_nih = False

[UPDATE]
timestamp = 1718999129

[S3]
profiles = "aws", "wasabi" ,"idrive"
default_profile = aws
archive_dir = froster
storage_class = INTELLIGENT_TIERING

[Profile aws]
provider = AWS
bucket_name = froster-dpcri

[Profile idrive]
provider = AWS
bucket_name = other

[Profile wasabi]
provider = Wasabi
bucket_name = something

storage_class could potentially move into the profile as well but it seems that AWS is currently the only provider that supports anything beyond STANDARD (but this could change in the future)

This is probably not needed as there is no case where AWS config and AWS credentials are in different folders, also we should not make this configurable as it would result in bad behavior such as putting creds in shared locations. It should always be in ~/.aws

[CREDENTIALS]
credentials_dir = /home/dp/.aws
profile = aws

dirkpetersen / froster

multi-profile options disappeared #90