jpillora / grunt-aws

A Grunt interface into the Amazon Node.JS SDK
171 stars 44 forks source link

task stalled #64

Closed fredguth closed 7 years ago

fredguth commented 7 years ago

created a very simple example Gruntfile.js

module.exports = function(grunt) {
  grunt.loadNpmTasks('grunt-aws');

  grunt.initConfig({
    aws: grunt.file.readJSON(".aws-credentials.json"),
    s3: {
      options: {
        accessKeyId: "<%= aws.accessKeyId %>",
        secretAccessKey: "<%= aws.secretAccessKey %>",
        bucket: "remoto-releases"
      },
      build: {
        cwd: "electron-out/make",
        src: "**"
      }
    }
  });
}

Then, I run:

$ grunt s3 -v
Initializing
Command-line options: --verbose

Reading "Gruntfile.js" Gruntfile...OK

Registering Gruntfile tasks.

Registering "grunt-aws" local Npm module tasks.
Reading /Users/fredguth/Code/remoto/remoto-app/node_modules/grunt-aws/package.json...OK
Parsing /Users/fredguth/Code/remoto/remoto-app/node_modules/grunt-aws/package.json...OK

Registering "/Users/fredguth/Code/remoto/remoto-app/node_modules/grunt-aws/tasks/services" tasks.
Loading "cloudfront.js" tasks...OK
+ cloudfront
Loading "route53.js" tasks...OK
+ route53
Loading "s3.js" tasks...OK
+ s3
Loading "sns.js" tasks...OK
+ sns
Loading "aws.js" tasks...OK
>> No tasks were registered or unregistered.
Loading "cache-mgr.js" tasks...OK
>> No tasks were registered or unregistered.
Reading .aws-credentials.json...OK
Parsing .aws-credentials.json...OK
Initializing config...OK
Loading "Gruntfile.js" tasks...OK
>> No tasks were registered or unregistered.

Running tasks: s3

Running "s3" task

Running "s3:build" (s3) task
Verifying property s3.build exists in config...OK
Files: , Remoto-1.1.53.dmg, Remoto-darwin-x64-1.1.53.zip
Options: access="public-read", concurrent=20, cacheTTL=3600000, dryRun=false, gzip, cache, overwrite, createBucket=false, enableWeb=false, signatureVersion="v4", accessKeyId="something", secretAccessKey="something", bucket="remoto-releases"
^C

(removed actual credentials values)

The task was stoped in this point for a while and didn't seem to progress.

fredguth commented 7 years ago

I had some progress when I inserted the region.

Running "s3:build" (s3) task
Verifying property s3.build exists in config...OK
Files: , Remoto-1.1.53.dmg, Remoto-darwin-x64-1.1.53.zip
Options: access="public-read", concurrent=20, cacheTTL=3600000, dryRun=false, gzip, cache, overwrite, createBucket=false, enableWeb=false, signatureVersion="v4", accessKeyId="AKIA...", secretAccessKey="Vv...", bucket="remoto-releases", region="us-west-2"
Warning: Put 'Remoto-darwin-x64-1.1.53.zip' failed...
PermanentRedirect: The bucket you are attempting to access must be addressed using the specified endpoint. Please send all future requests to this endpoint.
  Use --force to continue.

I don't see an endpoint configuration, shouldn't it define the right endpoint based on region?

fredguth commented 7 years ago

Well, I think i used wrong region, right one is 'us-east-1', so again back to the problem of stalling.