I’m trying to get the

vpcId

returned when creating a

cloud.Service

which is in

service.cluster.network.vpcId

if I export

service.cluster.network

I see the vpcId but I can’t for the life of me manage to get it in code to be able to use it to create other resources. Help!

is it something you need to

await

?

let me try, I’m actually creating the resources in a class constructor so awaiting is a little tricky, will do a little bit of refactoring

I don’t see much async/await in pulumi code

I’m trying to do something like this:

let service = new cloud.Service(name, {
    containers: {
        nginx: {
            image: "nginx",
            memory: 2048,
            ports: [
                { port: 80 },

            ],
        },
    },
    replicas: 1
});

let disco = new aws.servicediscovery.PrivateDnsNamespace("test", {
     description: "test",
     name: "test",
     vpc: service.cluster.network.vpcId.apply(v => v);
})

is that your actual code? because you have a semicolon where there should be a comma

which I would expect would raise TS errors

yeah I just hacked it together as a simple example, so might not be syntactically correct

right ok

What happens if you take out the

.apply(v => v)

? I'm doing similar stuff without using

apply

. pulumi seems to know how to wait for outputs when necessary

Yes - you shouldn’t need the apply with an identity function there

value is null

but it prints absolutely fine in an

exports

So

vpcId

there will be a

pulumi.Output<T>

, and the

vpc

parameter for PrivateDnsNamespace should be a

pulumi.Input<T>

, defined as (something like):

T | Promise<T> | Output<T>

I’m also having to cast to a

awsinfra.Network

to be able to get at the vpcId property

ah - that might be related

well I say cast, in TS land

Would

awsinfra.Network.getDefault()

work? Services created by pulumi use the existing default I believe

ah thats the whole point, I’m using a private Vpc (thats a whole new story)

ah-ha

putting inside an async function makes no different

I’ve throw the kitchen sink at it but just get

Missing required property 'vpc'

@tall-monitor-77779 so

service.cluster

is interface

CloudCluster

, which doesn't have a

network

prop, afaict: https://pulumi.io/reference/pkg/nodejs/@pulumi/cloud-aws/#CloudCluster

correct but if you trace the code back, a

awsinfra.Network

is passed and you can see it if you export the

service.Cluster

I dunno then 😞

I’ve created a simplified test if anyone wants to have a look

I think I have an idea what the issue may be

Give me a few mins and I’ll take a closer look

Team collaboration - so right now during a PoC - only way to share state is the Team edition?