docs(electron-publish): Mention the use of ~/.aws/config in electron-publisher s3 options #9018
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
It might seem like
electron-builder
orelectron-publish
do not support global aws credential configuration via~/.aws/config
file. They do but you have to specifyAWS_SDK_LOAD_CONFIG=1
env variable as the underlying Go SDK used for publishing does not load this file by defaultIn our use case we were trying to use IAM Identity Center SSO Credentials stored in
~/.aws/config
combined withAWS_PROFILE=
env variable. Took us quite some time to find how to achieve that. IMO this should be mentioned in the docs.If you're seeing:
this may apply to you