This message was deleted.

@little-river-49422 (what a name you have btw) you should be able to just depend on a promise with a timeout

yeah, i'm booting aks

If you rerun it, it usually works. It’s so annoying.

well, my name ensures unique identified for me across all the possible services on this planet 😉

that must be the old feature you look for in a name? lol

🤣

I forget the exact incantation… @bitter-oil-46081 you are good at javascript, if someone wanted to wait for like 10 or 20 seconds between two resource creations what woudl you do?

i suppose I can make everything depend on everything, so it takes as much time to do it

you should already be depending on the AD principal and stuff, I think

well, being unique is kinda important, yeah, nobody remembers how its spelled, but they always know its me 🙂

oh right

well, retry, if exists, wont be unique to python 😉

I was going to suggest some kind of

setTimeout

but that’s the wrong language

In js you can do the following:

function sleep(ms: number) {
                    return new Promise((resolve) => {
                        setTimeout(resolve, ms);
                    });
                }

And then await the promise.

But in Python… do they have promises?

mm, let me try something

So - just to be clear - this is a bug in the underlying Terraform Azure provider - and you should not have to manually wait. It is part of the contract of creating a resource that it is ready to be interacted with after completing creation. I believe we thought this was fixed with https://github.com/terraform-providers/terraform-provider-azurerm/pull/2204, but it seems like perhaps it is not. Regardless, it should be possible to add a wait per what @bitter-oil-46081 and @creamy-potato-29402 are suggesting - I just want to be clear that is working around a bug, not something you should need to do in the limit.

i know 😉