This message was deleted.

sparse-intern-71089

08/14/2019, 3:59 PM

This message was deleted.

best-xylophone-83824

08/14/2019, 4:02 PM

property is definitely there: https://www.pulumi.com/docs/reference/pkg/nodejs/pulumi/gcp/compute/#Subnetwork-name

best-xylophone-83824

08/14/2019, 4:02 PM

also strange that error doesn't show full type

gcp.compute.Subnetwork

, but just

Subnetwork

best-xylophone-83824

08/14/2019, 4:16 PM

basically trying to do:

Copy code

const neteng = new pulumi.StackReference(
    "org/gcp-neteng/prod"
).requireOutput("gke01London") as pulumi.Output<gcp.compute.Subnetwork>;


...
neteng.name;

and it fails. interestingly this change makes it work:

Copy code

).requireOutput("gke01London") as pulumi.Output<Pick<gcp.compute.Subnetwork,'name'>>;

white-balloon-205

08/14/2019, 5:07 PM

The outputs on `StackReference`s are plain JavaScript objects, not fully realized

Resource

instances. You typically need to output an id from one stack, and then

.get

that

id

in the other stack.

best-xylophone-83824

08/15/2019, 9:20 AM

as unknown as gcp.compute.Subnetwork;

works, but I agree that exporting just ID might be better

best-xylophone-83824

08/15/2019, 4:14 PM

I've found why it is like this. Basically

pulumi.Output<Resource>

leaves it with

OutputInstance<Resource>

without

& Lifted<T>

part, that is because of https://github.com/pulumi/pulumi/blob/8fd05fcd9fbd1480c01726b4fc7fcf158e611f99/sdk/nodejs/output.ts#L685 which skips recursing into object properties with

LiftedObject

. pulumi.Output<Pick<Resource, 'id'>> works because that

extends Resource<T>

becomes false and it recurses

best-xylophone-83824

08/15/2019, 4:15 PM

I'll create an issue for you to decide whether it is a bug , but it is definitely a usability problem

best-xylophone-83824

08/15/2019, 5:06 PM

https://github.com/pulumi/pulumi/issues/3096

Open in Slack

Previous Next

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.