Open Sytten opened 2 years ago
Thanks for your suggestion. Can you please elaborate on your use case and what you mean by injecting?
Basically digital ocean creates an access key and access key secret. So you can create a mock aws profile (without calling sts) and then you can do aws s3api get-bucket-lifecycle-configuration --bucket my-bucket --endpoint https://nyc3.digitaloceanspaces.com
.
I tried to use the AWS preset, but it seems like it does an operation (maybe calling sts?) that fails before setting up the credentials.
Is your feature request related to a problem? Please describe. It would be nice leapp supported digital ocean, specially for the S3 compatible API called Spaces.
Describe the solution you'd like Ideally just a store of the access key and access key secret as for other providers, then let the user decide where to inject them. Usually it is in aws credentials to be able to use the S3 CLI.
Describe alternatives you've considered Not storing credentials in leapp