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.

Pulumi Community

Looking at the types involved, I don’t see offhand why that shouldn’t work - how does it fail?

`awsCertificate.domainValidationOptions.resourceRecordName`: null

`awsCertificate.domainValidationOptions.resourceRecordValue`: null

This is unlikely to be related, but is there a reason you’re awaiting the constructor of the certificate?

to get the value for the verification dns record

I was able to get it with `awsCertificate.domainValidationOptions.apply`

Yeah, you shouldn’t need the await there - the constructors aren’t async - you’re better off allowing the data flow to do its thing there I think

I’ll put together a working example in a second, but to me it looks like it should be ok without the await

Yeah I guess await isn’t needed. the `.apply` is still needed though.

Yes, the apply may be needed right now. I think we could likely project something better there to remove the need for it