First time user, attempting to get a sample project up into aws but running into a problem with pulumi up. Using windows 10 (probably not the best approach) and the deploy seems to stall. Tried leaving it for hours with no luck. Anyone seen this type of hanging? Just stops at the line below.

I0322 22:24:05.056101   11760 plan_executor.go:391] planExecutor.retirePendingDeletes(...): no pending deletions
I0322 22:24:05.056101   11760 plan_executor.go:215] planExecutor.Execute(...): waiting for incoming events
I0322 22:24:05.056101   11760 step_executor.go:321] StepExecutor worker(-2): worker coming online
I0322 22:24:05.056101   11760 step_executor.go:321] StepExecutor worker(-2): worker waiting for incoming chains
I0322 22:24:06.757562   11760 eventsink.go:60] Registering resource: t=pulumi:pulumi:Stack, name=assettracking-testing, custom=false
I0322 22:24:06.757562   11760 eventsink.go:63] eventSink::Debug(<{%reset%}>Registering resource: t=pulumi:pulumi:Stack, name=assettracking-testing, custom=false<{%reset%}>)
I0322 22:24:06.762066   11760 eventsink.go:60] RegisterResource RPC prepared: t=pulumi:pulumi:Stack, name=assettracking-testing
I0322 22:24:06.762066   11760 eventsink.go:63] eventSink::Debug(<{%reset%}>RegisterResource RPC prepared: t=pulumi:pulumi:Stack, name=assettracking-testing<{%reset%}>)
I0322 22:24:06.762567   11760 source_eval.go:793] ResourceMonitor.RegisterResource received: t=pulumi:pulumi:Stack, name=assettracking-testing, custom=false, #props=0, parent=, protect=false, provider=, deps=[], deleteBeforeReplace=<nil>, ignoreChanges=[], aliases=[], customTimeouts={0 0 0}
I0322 22:24:06.762567   11760 source_eval.go:147] EvalSourceIterator produced a registration: t=pulumi:pulumi:Stack,name=assettracking-testing,#props=0
I0322 22:24:06.762567   11760 plan_executor.go:219] planExecutor.Execute(...): incoming event (nil? false, <nil>)
I0322 22:24:06.762567   11760 plan_executor.go:364] planExecutor.handleSingleEvent(...): received RegisterResourceEvent
I0322 22:24:06.762567   11760 step_generator.go:493] Planner decided to create 'urn:pulumi:testing::assettracking::pulumi:pulumi:Stack::assettracking-testing' (inputs=map[])
I0322 22:24:06.762567   11760 step_executor.go:321] StepExecutor worker(-2): worker received chain for execution
I0322 22:24:06.762567   11760 step_executor.go:321] StepExecutor worker(-2): worker waiting for incoming chains
I0322 22:24:06.762567   11760 step_executor.go:321] StepExecutor worker(0): launching oneshot worker
I0322 22:24:06.762567   11760 step_executor.go:321] StepExecutor worker(0): applying step create on urn:pulumi:testing::assettracking::pulumi:pulumi:Stack::assettracking-testing (preview true)
I0322 22:24:06.762567   11760 step_executor.go:321] StepExecutor worker(0): step create on urn:pulumi:testing::assettracking::pulumi:pulumi:Stack::assettracking-testing retired
I0322 22:24:06.762567   11760 source_eval.go:825] stripping unknowns from RegisterResource response for urn urn:pulumi:testing::assettracking::pulumi:pulumi:Stack::assettracking-testing
I0322 22:24:06.762567   11760 source_eval.go:835] ResourceMonitor.RegisterResource operation finished: t=pulumi:pulumi:Stack, urn=urn:pulumi:testing::assettracking::pulumi:pulumi:Stack::assettracking-testing, #outs=0
I0322 22:24:06.764569   11760 eventsink.go:60] RegisterResource RPC finished: resource:assettracking-testing[pulumi:pulumi:Stack]; err: null, resp: urn:pulumi:testing::assettracking::pulumi:pulumi:Stack::assettracking-testing,,,,
I0322 22:24:06.764569   11760 eventsink.go:63] eventSink::Debug(<{%reset%}>RegisterResource RPC finished: resource:assettracking-testing[pulumi:pulumi:Stack]; err: null, resp: urn:pulumi:testing::assettracking::pulumi:pulumi:Stack::assettracking-testing,,,,<{%reset%}>)

Any chance you can share you code? And if you are using JavaScript, your

node --version

?

I am trying to implement a Mapbox sample app using their template, https://github.com/mapbox/asset-tracking. Curently on node v12.16.1

This is most likely due to the issues in https://github.com/pulumi/pulumi/issues/3528. With Node 12 and newer, there can be hangs in Pulumi programs. We are making changes in Pulumi 2.0 (coming in a few weeks) to prevent the patterns that trigger this. Ahead of that - you can either use Node.js 10, or can update your code to replace this:

//* Specify your IoT Channel to consume in the front-end.
//* This enables real-time updates in browser.
//* The API Gateway will also provide a batch request as needed.
const iotFrontEnd = "frontend";
const getIoTArn = async channel => {
  const current = await aws.getCallerIdentity({});
  const region = await aws.getRegion();
  const iotArn = `arn:aws:iot:${region.name}:${current.accountId}:topic/${channel}`;
  return iotArn;
};
//* Set your AWS IoT Endpoint - this is used to generate the IoTHarness
const IoTEndpoint = aws.iot.getEndpoint({ endpointType: "iot:Data-ATS" })
  .endpointAddress;

With this:

//* Specify your IoT Channel to consume in the front-end.
//* This enables real-time updates in browser.
//* The API Gateway will also provide a batch request as needed.
const iotFrontEnd = "frontend";
const getIoTArn = channel => {
  const current = pulumi.output(aws.getCallerIdentity({ async: true}));
  const region = pulumi.output(aws.getRegion({}, { async: true}));
  const iotArn = pulumi.interpolate`arn:aws:iot:${region.name}:${current.accountId}:topic/${channel}`;
  return iotArn;
};
//* Set your AWS IoT Endpoint - this is used to generate the IoTHarness
const IoTEndpoint = pulumi.output(aws.iot.getEndpoint({ endpointType: "iot:Data-ATS" }, { async: true }))
  .endpointAddress;

Thanks for the reply! I will give this a go!