This message was deleted.

Hi. I'm not sure that this is an AWS-specific question. Why are you calling

apply()

on name? What are you doing with the name; is it being passed into a constructor of a Pulumi resource? You don't need to call

apply()

in this case.

Well this is not AWS specific question, i apologize. This is more regarding pulumi. I am using

apply()

here for some specific reason. When the Autoscaling class will create multiple instance of asg groups eg

idx1. iidx2...n

on each instance,

apply()

will be called on each instance class and start creating EC2 tags for example for ’idx1" instance class, it will create tags as

idx1-1, idx1-2, idx1-3..n

.

Often the code can be written so that the

apply()

(or

interpolate()

) is performed on parameters to the constructor. If it's possible, then this will at least eliminate a potential source of issues. Here's an example from the Pulumi examples repo: https://github.com/pulumi/examples/blob/71a705e12b1ea6b132ecf164f0a71adabc78b4ce/aws-py-apigateway-lambda-serverless/__main__.py#L78

I guess the example you referred is quite different and not related the way i want. Here i am trying to accomplish synchronous call with every loop of instance calling

apply()

, but in a loop it picks the last element and execute

apply()

rather it has to go through each element and call

apply()

Technically, it won't ever be synchronous. The loop will finish before the engine is invoked. In Pulumi, your code builds state, and after the state is fully built, the Pulumi engine makes the provider look like your state. That said, there shouldn't be any problem doing it either way. You can loop over all the resources and create new resources from them, whether you're inside an

apply()

or not. I'm not familiar with Python's scoping rules, they may be throwing a spanner in the works here. Maybe the question could be asked in #CDE799L1M, along with the looping code that isn't working for you?