docs(electron-publish): Mention the use of ~/.aws/config in electron-publisher s3 options#9018
Merged
mmaietta merged 4 commits intoelectron-userland:masterfrom Apr 10, 2025
Conversation
🦋 Changeset detectedLatest commit: c3848d3 The changes in this PR will be included in the next version bump. This PR includes changesets to release 12 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
Contributor
Author
|
I think the labels should mention |
Collaborator
|
Thanks for adding to the docs! Could you please regenerate the schema using |
Contributor
Author
|
Done |
This was referenced Apr 10, 2025
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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-builderorelectron-publishdo not support global aws credential configuration via~/.aws/configfile. They do but you have to specifyAWS_SDK_LOAD_CONFIG=1env 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/configcombined 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