https://pulumi.com logo
l

loud-nest-15724

07/24/2019, 6:12 PM
hey all, hope this is the right place to ask this question. I'm trying to use the s3 website sample from the examples repo, but I'm getting an error when trying to preview or deploy a stack
Copy code
Previewing update (testing):

     Type                 Name                      Plan     Info
     pulumi:pulumi:Stack  aws-js-s3-folder-testing           1 error; 13 messages

Diagnostics:
  pulumi:pulumi:Stack (aws-js-s3-folder-testing):
    error: Unrecognized flag --query-mode
    usage: RUN <flags> [program] <[arg]...>
        where [flags] may include
            --project=p         set the project name to p
            --stack=s           set the stack name to s
            --config.k=v...     set runtime config key k to value v
            --parallel=p        run up to p resource operations in parallel (default is serial)
            --dry-run           true to simulate resource changes, but without making them
            --pwd=pwd           change the working directory before running the program
            --monitor=addr      [required] the RPC address for a resource monitor to connect to
            --engine=addr       the RPC address for a resource engine to connect to
            --tracing=url       a Zipkin-compatible endpoint to send tracing data to
        and [program] is a JavaScript program to run in Node.js, and [arg]... optional args to it.

    error: an unhandled error occurred: Program exited with non-zero exit code: 255
the version of the pulumi cli is v0.17.25 and the node version is v10.16.0
b

broad-football-5123

07/24/2019, 6:16 PM
That is interesting. It’s doing that every time you run
pulumi up
? Did you get a preview?
l

loud-nest-15724

07/24/2019, 6:17 PM
yes, the preview gives the same response
b

broad-football-5123

07/24/2019, 6:17 PM
Are you just running
pulumi up
with no other flags?
l

loud-nest-15724

07/24/2019, 6:19 PM
yep, not added any flags
I can run other pulumi programs and deploy them
b

broad-football-5123

07/24/2019, 6:21 PM
So it’s just happening for this example. Curious.
l

loud-nest-15724

07/24/2019, 6:23 PM
I've seen it on this one and also the s3-folder component example, which I guess is very similar code
b

broad-football-5123

07/24/2019, 6:24 PM
Have you successfully created an S3 bucket before?
I was just able to run it on my machine.
l

loud-nest-15724

07/24/2019, 6:27 PM
yes, I've created s3 buckets in other stacks
b

broad-football-5123

07/24/2019, 6:28 PM
what if you run
pulumi up -d
l

loud-nest-15724

07/24/2019, 6:28 PM
It's the website functionality which I've not got working in my stack which is why I want to check the examples to see how that is done
I'm getting the same output with -d
b

broad-football-5123

07/24/2019, 6:36 PM
Did you make any changes to the example code?
l

loud-nest-15724

07/24/2019, 6:39 PM
no, just checked and I've got the latest code from master
b

broad-football-5123

07/24/2019, 6:40 PM
What if we run
pulumi up -v 3
to up the verbosity. Trying to find a helpful error.
l

loud-nest-15724

07/24/2019, 6:47 PM
I've got the deploy working now. I deleted the node_module and re-ran yarn install
I assume it was something to do with an old dependency, I remember I've tried running this code before ages ago with an older version of pulumi
b

broad-football-5123

07/24/2019, 6:50 PM
Oh interesting.
l

loud-nest-15724

07/24/2019, 6:55 PM
thanks for the suggestions and the quick feedback
👍 1