This message was deleted.

Found it. The example code from the

getDirectory

function was a good start. This is passing tests:

const dnsIpAddresses = this.ad.id.apply(async (directoryId) => {
      const result = await aws.directoryservice.getDirectory({ directoryId: directoryId }, { async: true });
      return result.dnsIpAddresses;
    });

(It's not deployed yet, so I might be back later for more help 🙂 )

dnsIpAddresses

is an output of

aws.directoryservice.Directory

- https://www.pulumi.com/docs/reference/pkg/aws/directoryservice/directory/#dnsipaddresses_nodejs. You should be able to export/output this directly or use this as an input to other resources. So you should not need to use

getDirectory

after the fact. Is this not working for you?

I don't think so. I'm having a lot of issues with dnsIpAddress fields all over the place. I used this workaround because those fields weren't being populated. I can't use them in VpcDhcpOptions either, they're not even getting into that. If I pass the the dnsIpAddresses returned as outputs (that I can see in my test breakpoints) into VpcDhcpOptions

domainNameServers

,

ntpServers

and

netbiosNameServers

input args, they're not there when I break in

setMocks

with type = "awsec2/vpcDhcpOptionsVpcDhcpOptions". The other args fields are there, like

netbiosNodeType

, but the 3 servers fields are gone.