This message was deleted.

You will need to do that within the apply!

I'm all set now, I was struggling originally because I was trying to do something like:

test = '''{{ some_value }}'''
jinja2.Template(test).render(
  some_value = pulumi_output.apply(lambda x: f"{x}"
))

and similar incantations, which was not working adjusting to treat the apply as the entrypoint e.g.

test = '''{{ some_value }}'''
pulumi_output.apply(
  lambda x: jinja2.Template(test).render(some_value=x))

works just fine 🙂

hey Rob, is there any reason you don't want to use

apply

as the entrypoint? you have to do it that way, because

apply

basically means "wait for this value to resolve, then do something"

no reason I was just misunderstanding how it worked

give this a read and see if it helps https://www.leebriggs.co.uk/blog/2021/05/09/pulumi-apply.html

will do thanks!

Not only yours mate 🙂 I usually have the same approach when I'm learning a new tool. Just drop into the debugger and see what I can touch. I suspect this happens because Pulumi promises that you can use the language of your choice but after that, you discover that you may be writing the language but Pulumi dictates how you write it. I find it difficult to adjust as well. I also believe if this can be fixed it will unleash the true potential Pulumi has. However it will probably take some time