pulumi-community #python

little-river-49422

02/14/2019, 9:42 PM

else how would you explain the fact that if you run it in pieces it works?

little-river-49422

02/14/2019, 9:43 PM

you can try with application\service principal piece

little-river-49422

02/14/2019, 9:43 PM

its pretty short and seems to have the same flaw

little-river-49422

02/14/2019, 9:44 PM

i mean, i dont see any other logical end I can come to when I observe such behaviour

incalculable-sundown-82514

02/14/2019, 9:48 PM

I don’t have an azure setup, give me a minute to check it out

little-river-49422

02/14/2019, 9:49 PM

hey, no haste at all, i'm just trying to figure out of its me or pulumi 🙂

little-river-49422

02/14/2019, 9:49 PM

i'm going to sleep anyway. just tell me what you think 😉 when you have something 😉

incalculable-sundown-82514

02/14/2019, 9:52 PM

sure! It would be super helpful if you could minimize the repro, though - it’s hard to do that when the repo involves cloud resources. I try to use the

pulumi_random

package to reproduce bugs since it doesn’t talk to cloud services.

incalculable-sundown-82514

02/14/2019, 9:53 PM

in this case it’s possible that we’re failing to connect the

id

field on `Subnet`; if that’s the case then it should manifest for other resources, as well, which is puzzling.

little-river-49422

02/14/2019, 9:55 PM

I'm not sure how to use pulumi_random because we seem to have a problem with these particular resources only?

little-river-49422

02/14/2019, 9:55 PM

all the other "linkings" are fine

incalculable-sundown-82514

02/14/2019, 9:56 PM

The same code handles all of the resources; there’s nothing special about

ServicePrincipal

here.

id

is treated specially by the Pulumi runtime, so that’s interesting

incalculable-sundown-82514

02/14/2019, 9:56 PM

I’ll check it out when I get an azure setup

little-river-49422

02/14/2019, 9:57 PM

well, i understand that that's the same code behind this. but i think its some edge case?

little-river-49422

02/14/2019, 9:57 PM

its the

.id

in both cases causing it to hiccup**

little-river-49422

02/14/2019, 9:58 PM

lol

little-river-49422

02/14/2019, 9:58 PM

from what I got from the docs

.id

is the internal identifier

little-river-49422

02/14/2019, 9:58 PM

and its getting rewritten (questionmark) by the resource output

little-river-49422

02/14/2019, 10:00 PM

ok, really gotta go sleep, its 1am here. later folks, good luck

incalculable-sundown-82514

02/14/2019, 10:33 PM

OK, I think I might know what the problem is - digging in further

incalculable-sundown-82514

02/14/2019, 10:49 PM

figured it out, here’s a fix: https://github.com/pulumi/pulumi/pull/2449

incalculable-sundown-82514

02/14/2019, 10:50 PM

we’ll get this merged over the next day or two

incalculable-sundown-82514

02/14/2019, 10:52 PM

tracking issue: https://github.com/pulumi/pulumi/issues/2450

little-river-49422

02/15/2019, 5:33 AM

partypus

little-river-49422

02/15/2019, 3:39 PM

will this fix contain the previous one (whatever it was)

little-river-49422

02/15/2019, 3:39 PM

ah, never mind. previous one was pulumi_kubernetes

incalculable-sundown-82514

02/15/2019, 5:55 PM

just merged the fix, once the CI finishes up you should be able to do

pip install --pre pulumi

and get the fix

incalculable-sundown-82514

02/15/2019, 5:55 PM

(CI takes about 30 minutes or so)

little-river-49422

02/15/2019, 9:03 PM

hey folks, can you educate me how to create a new tutorial for azure? on your docs site

little-river-49422

02/15/2019, 10:05 PM

stupid question, is there a way to wait in pulumi? i'm hitting a problem where pulumi cannot detect the azure ad application, i suspect its a race, because if I rerun it works fine