Closed fredguth closed 7 years ago
@fredguth I can see a potential issue in the code for handling this but not if you've set the secretAccessKey
option correctly. Can you triple double backwards check that that option is actually set to a non-empty string 😄
@fredguth Can you response to the above 😄
Since the original issue reporter has not responded to the request for additional information in about two weeks, I'm going to assume that they either found the answer in another manner or decided not to pursue this issue. If I'm incorrect, they can respond with answers to the questions posed, and I'll reopen.
Please describe your issue: Although I have no problem on publishing on Github, I can't publish on S3.
*Console output when you run
electron-forge
with the environment variable `DEBUG=electron-forge:`. (Instructions on how to do so here). Please include the stack trace if one exists.** ...What command line arguments are you passing?
What does your
config.forge
data inpackage.json
look like?Please provide either a failing minimal testcase (with a link to the code) or detailed steps to reproduce your problem. Using
electron-forge init
is a good starting point, if that is not the source of your problem.I am using ember-electron, an it is using electron-forge. Don't know how to build a simple testcase, sorry. I believe the problem is not in the ember-electron part, as I can "make" and also "publish to github".
I have tried before with "accessKey" instead of "accessKeyId", but I believe the README.md I was seeing with "accessKey" was old documentation by what I saw here: https://github.com/electron-userland/electron-forge/issues/143 and here: https://github.com/electron-userland/electron-forge/blob/master/src/publishers/s3.js#L19.
I do have AWS_SECRET_ACCESS_KEY in my environment: