Hi, I'm hoping for some guidance on how to correctly implement the following... I am deploying an Integration Runtime to an Azure Data Factory using Pulumi.AzureNative.DataFactory.IntegrationRuntime. Once the integration runtime has been deployed I then need to obtain the AuthKey from it. There is a function for this ( Pulumi.AzureNative.DataFactory.ListIntegrationRuntimeAuthKeys) but it requires the Integration Runtime Name to be specified as a string. The Integration Runtime deployment returns an object with a Name property of type Output<string> which the ListIntegrationRuntimeAuthKeys won't accept. I am guessing that I need to make use of something like Apply here to get the name back as a string but am unsure how to do it in such a way that I get the authKey correctly returned (also as a string not an Output<string>)? This doesn't work for example as authKey is only available within the Apply block and I need it available outside of that (so I can pass it in to another deployment that also wants it as a string)

integrationRuntime.Name.Apply(n =>
{
    var authKey = Pulumi.AzureNative.DataFactory.ListIntegrationRuntimeAuthKeys.InvokeAsync(new Pulumi.AzureNative.DataFactory.ListIntegrationRuntimeAuthKeysArgs
    {
        FactoryName = runtimeSettings.DataFactoryName,
        ResourceGroupName = runtimeSettings.DataFactoryResourceGroup,
        IntegrationRuntimeName = n
    }).Result.AuthKey1;
    return n;
});

You can’t get a

string

from

Output<string>

because you’d loose the dependency tracking then. Why do you need your auth key to be a plain string? You can usually pass outputs as inputs to other resources.

I need to pass the auth string in as part of a powershell command in a VirtualMachineExtension deployment. The args for that have a ProtectedSettings property which takes a dictionary<string,.string>. I need to add an entry to that with key = "commandToExecute" and value = "the powershell command including the auth key"

Then you need to build the dictionary inside another Apply

OK so I take it you mean that the VirtualMachineExtension deployemnt would have to also run within the Apply. This is how I have it at the moment but the pulumi docs warn against creating new resources inside of Applys so I was trying to refactor it. I take it that this is unavoidable in this scenario? Apply Docs

No, the resource won’t be inside an Apply. Resource properties are always inputs which accept outputs.

ah OK, I'll give that a go, thanks

That looks correct until we land https://github.com/pulumi/pulumi/issues/7945 where functions will accepts outputs. The only change I suggest is an await

var commandToExecute = myIR.Name.Apply<string>(async name =>
{
    var authKey = (await Pulumi.AzureNative.DataFactory.ListIntegrationRuntimeAuthKeys.InvokeAsync(new Pulumi.AzureNative.DataFactory.ListIntegrationRuntimeAuthKeysArgs
    {
        FactoryName = "dfname",
        ResourceGroupName = "rgname",
        IntegrationRuntimeName = name 
    })).AuthKey1;

    var commandToExecute = $"powershell.exe -ExecutionPolicy Unrestricted -File gatewayInstall.ps1 {authKey}";

    return commandToExecute;
});

thanks for your help