https://pulumi.com
Join Slack
Menu
Home
Archive
This message was deleted.
# aws
s
This message was deleted.
i
Here were the outputs from the previous run to show that it did launch the first time:
Copy code
Outputs:
  - vpcId            : "vpc-0f42382f75c6d7a70"
  - vpcPrivateSubnets: [
  -     [0]: "subnet-0634fa67343a153e7"
  -     [1]: "subnet-0bb0cbf6bc1078b1b"
    ]
  - vpcPublicSubnets : [
  -     [0]: "subnet-0a7f9f9da8c3043e6"
  -     [1]: "subnet-0fe54f1016b4aa906"
    ]
My tsconfig
Copy code
{
  "compilerOptions": {
    "strict": true,
    "outDir": "bin",
    "target": "es2016",
    "module": "commonjs",
    "moduleResolution": "node",
    "sourceMap": true,
    "experimentalDecorators": true,
    "pretty": true,
    "noFallthroughCasesInSwitch": true,
    "noImplicitReturns": true,
    "forceConsistentCasingInFileNames": true
  },
  "files": [
    "index.ts"
  ]
}
i haven't made any changes to the tsconfig or the sample code, i just simply tried to run it a second time.
l
What version of awsx are you using?
i
pulumi 3.34.1 awx 0.40.0 they were the default installed when using the one-line install
and aws 5.8.0, in case it matters if i upgrade awsx version
i'm sort of confused why it would work once and then fail the second time
if i destroy and delete the stack, and then provision again, it works, but then fails on subsequent runs again
l
awsx 0.40 is the old version; all the docs still describe it, it's what I use. I don't think subnetSpec is part of that API, is it? I can't see it, I see just `subnets`: https://www.pulumi.com/docs/reference/pkg/nodejs/pulumi/awsx/ec2/#VpcArgs-subnets
Where did you see 
subnetSpec
?
i
half way down the page under "Configuring Subnets for a VPC"
maybe the documenation was updated early?
l
Yea maybe, let's find the API for awsx 1.0.
i
l
Yep, I see SubnetSpec in there. Try changing your awsx version in package.json
i
i know its a beta, but its like beta 8, to me that would seem fairly stable?
maybe you're right and i should just push the version forward
l
It's either that or change the syntax to be 0.40 compliant. It's very similar, a minor change.
I'd roll forward though.
i
as a first experience, this does not spark joy
l
You missed 
nodejs
i
cheers
it looks like the path changed during that upgrade as well, 1.0.0 is no longer in nodejs folder
👍 1
Thanks for your help @little-cartoon-10569 👍 super appreciated sir. You provided me with a new way to discover issues as well, I didn't go read the code before but this broke the ice.
👍 1
Open in Slack
PreviousNext
Powered by

Pulumi Community

No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Powered by