You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
+1
Using environment variables is the way to go for bitbucket pipelines (and maybe other CI tools and Pupppet-managed configurations, docker images etc... as well). I believe it's safer that way because it decouples platform configuration from the application.
Requiring the use of only either ~/.s3cfg or environment variables is limiting, it would be nice to fall back to the official AWS SDK's credentials configuration strategy: http://docs.aws.amazon.com/AWSJavaScriptSDK/guide/node-configuring.html
It supports the environment variables too, but also switching profiles, loading from the ~/.aws configuration directory, and all that.
The text was updated successfully, but these errors were encountered: