@tall-librarian-49374 would love your thoughts on that ☝️ I was on a call with @worried-knife-31967 and could see some weird behaviour

I can’t remember trying this but I can’t see why it shouldn’t work. Any details on the weird behaviour?

@worried-knife-31967 wanna post the gist here?

And what happens then? Does the program succeed/fail? Do you get the output?

Odd that it makes it past the first await but not the second?

it didn't actually create the key, but now it won't run it as the resource has been created. If I change the inputs (i.e. the key name and value) it doesn't recreate the resource either

Which resource? This should run regardless of whether a resource is already created or not.

Also I don't know that this is affecting anything, especially since you're only getting to

got 5

, but it's throwing me off a little bit that line 61 of the gist is assigning to

this.Key

when the constructor already did that

A combination of all the above seems to have done it 😄

so

RegisterOutputs

internally adds the task to a collection of tasks to be awaited. the issue before was your task wasn't being awaited so the program was exitting before it could finish. Also when you pass

CreateAsync

that task starts running immediately, which is why you are seeing it run before you apply

That makes sense. So how do I stop the webrequest from running as part of the first phase, and make it run only after the yes part?

I think you are correct that checking

IsDryRun

will do that for you

args.Name shouldn’t resolve until the function app is created, if I read the code correctly

it's more that it's running everytime I do

pulumi up

As the code currently exists you will create a new key on every deploy. I think what you might be looking for is a

dynamic provider

which would handle not creating if it already exists, updating it, etc.. unfortunately not supported in .NET right now

ComponentResource

is mostly meant to be used to encapsulate the deployment of a logical grouping of cloud resources. But you're trying to give pulumi the ability to manage/provision a custom resource (your function key) so you want a provider

Agreed. This is a custom resource-level thing. In theory, this could be a custom resource inside the provider, or in a separate library, implemented once and generated for all languages. Obviously, it’s a larger commitment, but the tech is there.

I've done this for now...

if (Pulumi.Deployment.Instance.IsDryRun)
        {
            var dryRunResponse = await httpClient.GetAsync(new Uri($"/admin/host/keys/{keyName}", UriKind.Relative));
            if (dryRunResponse.IsSuccessStatusCode)
            {
                var getkeyresponse = JsonSerializer.Deserialize<GetKeyResponse>(await dryRunResponse.Content.ReadAsStringAsync());
                if (keyValue == getkeyresponse.Value)
                    return keyValue;
            }

            return "";
        }

yes, DryRun is a preview