This message was deleted Pulumi Community #general

Join Slack

This message was deleted.

# general

sparse-intern-71089

08/04/2018, 5:39 PM

This message was deleted.

stocky-spoon-28903

08/04/2018, 5:40 PM

That makes sense. I set

parent

of all of the resources to the component instance, but don’t set the component instantiation itself

big-piano-35669

08/04/2018, 5:40 PM

It is supposed to pick up the global

Stack

component if you don't specify one, so you did the right thing here.

stocky-spoon-28903

08/04/2018, 5:41 PM

Ah, I see. Is there a way to set it explicitly in the meantime?

stocky-spoon-28903

08/04/2018, 5:41 PM

Having the visualization would be pretty nice for demoability

big-piano-35669

08/04/2018, 5:43 PM

You can try:

Copy code

import { runtime } from "@pulumi/pulumi";

...

new SomeResource(..., { parent: runtime.getRootResource() });

This might work, depending on the nature of the bug. If the bug is that we're erasing the root resource (

Stack

) too soon, then this might lead to the same result.

big-piano-35669

08/04/2018, 5:43 PM

Btw, do you have a repro program that I can link to in the bug?

stocky-spoon-28903

08/04/2018, 5:44 PM

Yes

stocky-spoon-28903

08/04/2018, 5:45 PM

I don’t have a minimal one right now but can make one if necessary

stocky-spoon-28903

08/04/2018, 5:46 PM

https://gist.github.com/jen20/83256db5b6a3d4bc6c948c5116e32f06

big-piano-35669

08/04/2018, 5:47 PM

Ok, great, I filed https://github.com/pulumi/pulumi/issues/1704 to track.

stocky-spoon-28903

08/04/2018, 5:47 PM

👍 The repro is not the easiest thing to run, because it relies on having a public hosted zone with the given domain name available

stocky-spoon-28903

08/04/2018, 5:47 PM

I suspect any component resource used at the top level would do this though?

big-piano-35669

08/04/2018, 5:48 PM

I have a feeling this might be a problem if you end up with multiple copies of the

@pulumi/pulumi

module loaded. This can happen depending on how NPM decides to resolve semvers. One last thing you could do to help determine if this is the issue; can you run

find node_modules -name 'pulumi

from the root of your program, and let me know what it returns?

stocky-spoon-28903

08/04/2018, 5:49 PM

Copy code

~/Code/pulumi/pulumi-vault-test master*
❯ find node_modules -name 'pulumi'
node_modules/@pulumi/pulumi

stocky-spoon-28903

08/04/2018, 5:49 PM

However, some of the dependencies are installed via

npm link

, so it also has a copy of

@pulumi/pulumi

there

big-piano-35669

08/04/2018, 5:50 PM

Ahh, does

find -L node_modules -name 'pulumi'

print multiple?

stocky-spoon-28903

08/04/2018, 5:50 PM

They are likely different versions too, since the module depends on the latest stable release, and I’m running something close to

master

stocky-spoon-28903

08/04/2018, 5:51 PM

Yes, following links shows 2, somewhat as expected:

stocky-spoon-28903

08/04/2018, 5:51 PM

Copy code

❯ find -L node_modules -name 'pulumi'
node_modules/@pulumi/pulumi
node_modules/@operator-error/pulumi-lambda-cert/node_modules/@pulumi/pulumi

big-piano-35669

08/04/2018, 5:51 PM

Ah, ok, this must be it. Obviously this should work, but because each copy of the loaded module gets its own statics, what I think is happening is that the root resource gets created in one copy but not the other. Hence, the blank parent. cc @incalculable-sundown-82514

big-piano-35669

08/04/2018, 5:51 PM

We will need to think about this one, I'll add notes to the bug.

stocky-spoon-28903

08/04/2018, 5:53 PM

Sounds good, thanks for confirming it’s a bug.

stocky-spoon-28903

08/04/2018, 5:53 PM

There was a second thread semi-concurrent with this one about values in a map not being tracked for pulumi update - not sure if you noticed that one too?

stocky-spoon-28903

08/04/2018, 5:54 PM

Also, FWIW, setting the parent to

runtime.getRootResource()

works great:

big-piano-35669

08/04/2018, 5:56 PM

Awesome! Unfortunately, this means I don't actually understand the root cause as well as I thought, because that shouldn't have worked based on my theory 🙂 Oh, well, glad you at least have a workaround for now!

stocky-spoon-28903

08/04/2018, 5:58 PM

Yes, this definitely solves the problem for now

👍 1

stocky-spoon-28903

08/04/2018, 7:29 PM

@big-piano-35669 There is a weird side effect in the plan output of doing this though:

stocky-spoon-28903

08/04/2018, 7:29 PM

Copy code

Type                                           Name                                    Plan       Info
 +   pulumi:pulumi:Stack                            pulumi-vault-test-vault-test-dev        create.
 +   ├─ operator-error:aws:LambdaCert               algo-vault-lambda-cert                  create
 +   │  ├─ aws:iam:Role                             algo-vault-lambda-cert-function-role    create
 +   │  │  └─ aws:iam:RolePolicy                    algo-vault-lambda-cert-function-policy  create
 +   pulumi:pulumi:Stack                            pulumi-vault-test-vault-test-dev        create..
 +   │  ├─ aws:s3:Bucket                            algo-vault-lambda-cert-bucket           create
 +   │  ├─ aws:lambda:Function                      algo-vault-lambda-cert-function         create
 +   │  │  └─ aws:lambda:Permission                 algo-vault-lambda-cert-permission       create
 +   pulumi:pulumi:Stack                            pulumi-vault-test-vault-test-dev        create
 +   │     └─ aws:cloudwatch:EventTarget            algo-vault-lambda-cert-target           create
 +   ├─ operator-error:aws:Vpc                      algo-vault                              create
 +   │  └─ aws:ec2:Vpc                              algo-vault-vpc                          create
 +   │     ├─ aws:ec2:VpcDhcpOptions                algo-vault-dhcp-options                 create
 +   │     │  └─ aws:ec2:VpcDhcpOptionsAssociation  algo-vault-dhcp-options-assoc           create
 +   │     ├─ aws:ec2:InternetGateway               algo-vault-igw                          create
 +   │     ├─ aws:route53:Zone                      algo-vault-private-hosted-zone          create
 +   │     ├─ aws:iam:Role                          algo-vault-flow-logs-role               create

stocky-spoon-28903

08/04/2018, 7:29 PM

(output is shortened, but you can likely see the repetition of the Stack in the output)

4 Views

Open in Slack

Previous Next