How many folks place pulumi resources inside a

.apply

of another resource to ensure you get the proper

string

type you want, where if you didn’t, you’d most likely get an error of undefined. I do this all the time, but on a net new stack, pulumi won’t show the resources to be created inside that

.apply

which makes sense to me, but also very hard as some of these resources I want to import before my pulumi up and can’t verify they are imported

not sure if i understand the problem 100% here, but could you not use

dependsOn

to achieve this?

well I’d be using the string as a conditional

ok got you, are you hitting a race condition where the resource isnt imported? or is it just a concern? i cant imagine pulumi would execute that code without the resource being there

yea it’s tough one where using a 3rd party provider (we created) and earlier work was done via the console, so now we want it behind code

i was trying to use imported resources just for github repos and config and it was a nightmare, luckily i work at a startup so we have built everything. my approach would be to get some downtime in to recreate things 😬

honestly, we’ll probably just do a 2nd run, where we build everything but what we need, and then add in the imported resources when the promise is known

let me see how i handled the imports first in what i was doing, deleted the code now but should be in git somewhere

place pulumi resources inside a .apply of another resource to ensure you get the proper string type you want

This is never be necessary, and (imo) always wrong. You can use the output properties of the first resource in the 2nd resource without a problem.

you can provide a working example?

Of using a resource's outputs in another resource? All the example code should do that.. have you browsed github.com/pulumi/examples?

are you familiar with promises?

Yes.

ok, then you know this doesn’t just work on using new resources

It does. Pulumi takes care of it for you.

this isn’t just the output from one pulumi to pulumi input type by the 2nd

Ah, sorry. Can you explain in more detail then? Example code, perhaps?

it’s getting a promise back from a library and using the promised string type value as a conditional value to do more things

Promises are in the Input union type, you can use them like outputs.

this is part of code that is NOT a pulumi resource, it’s being used to decide which pulumi to create next

Can I ask: ideally, would you be creating all the resources? And you're using the promised value to decide whether or not you have enough information to do it now?

I don't think I'm gleaning enough from that. You can use get-methods and imports to avoid putting anything inside a .then() or .apply(). It's not always obvious, but in my experience, it's always possible.

here is some code

// Call MBX EC2 Library
	const asg = new mbxec2.ASG({
	...does things
	)}

	// Build DNS Entries for Ultra DNS & CloudFlare
	asg.loadBalancer.dnsName.apply((albDnsName) => {
		// AWS ALB Specific Record per Environment
		if (env.appEnv.includes('-example')) {
			config.ultraDnsRecords.map((ultraRecord) => {
				new ultradns.Record(`${env.appEnv}-${ultraRecord.subDomain}-ultraDnsRecord`, {
					ownerName: ultraRecord.subDomain,
					recordType: 'CNAME',
					zoneName: config.bookerTld,
					ttl: 3600,
					recordDatas:
						ultraRecord.data == 'ALB-DNS-PLACEHOLDER' ? [`${albDnsName}.`] : [`${ultraRecord.data}`]
				});
			});

do you return the outputs in the library? by extending the pulumi componentresource class

unfortunately the ultraDNS provider wants an array of strings

Can you not move the use of loadBalancer.dnsName down to inside recordDates?

if you just use

asg.loadBalancer.dnsName

in the recordDates I would get undefined

If the output is resolved inside the constructor parameters, then you don't have to call the constructor inside an apply.

w/o the apply

So is the problem that ultraRecord is somehow not a promise, but not available until after dnsName's promise resolves?

correct

Then make it a promise.

yea we only get an alb Dns name once the resource is created

And it would be as simple as

const ultraPromised = lb.name.apply((_) => ultraReal))

I will try what you suggest, but feel like it will leave me right back where I started. Thanks all for the feedback!

There is one exception to this rule, and Pulumi have fallen victim to it themselves:

@elegant-crayon-4967

unfortunately the ultraDNS provider wants an array of strings

It seems that the

recordDatas

property takes in an

Input

of array of

Input<string>

. So you should be able to use the ALB's

dnsName

property directly as @little-cartoon-10569 suggested.

Input

is a type union:

export declare type Input<T> = T | Promise<T> | OutputInstance<T>;

if you just use

asg.loadBalancer.dnsName

in the recordDates I would get undefined

I think this might provide a hint as to what might be wrong here. How is the

loadBalancer

property getting its value in the component resource

mbxec2.ASG

? Also are you calling

super.registerOutputs({})

in your component resource after you've created all the resources you need to?