I think that's a good idea. I had thought of it in the past as well.
Now, do you think about going as far as specifying a secondary set of connection settings along with separate credentials? That could be challenging given how we handle connections in Medusa.
Now, if it's just about specifying a different bucket name but reusing the same credentials, I guess that could be simpler (although we'd have to double check this).

If you feel like contributing this feature, it would be much appreciated :)
I guess we'd need to see how this could be designed first though.

@adejanovski Hi! Thanks for the answer. I made PR #590 with my implementation of this feature.

1. Should we also configure prefixes from args?
2. About keys, I think that we should not use separate keys here. General best practice for cloud - using SA attached to a host, without SA keys, and in this case, we cannot attach two SA.

oh, I couldn't see the linked PR from the ticket because of how the ticket was referred to in the description (see this).

I'll add the review to my todo list.

Should we also configure prefixes from args?

I think it would be nice indeed.

About keys, I think that we should not use separate keys here. General best practice for cloud - using SA attached to a host, without SA keys, and in this case, we cannot attach two SA.

I agree 👍

@adejanovski

I think it would be nice indeed.

I added a configurable prefix.