Hi, I got a stack consisting of about 20 resources. I used it in the past and it worked fine. Now I'm trying to run

pulumi preview

on a clean slate, ie with no resources up yet and I get the following error:

Diagnostics:
  pulumi:pulumi:Stack (Cloud-dev):
    error: Running program 'C:\Projects\Deon\infrastructure\azureresources' failed with an unhandled exception:
    Error: invocation of azure-native:cache:listRedisKeys returned an error: request failed /subscriptions/25110286-d288-4e46-851b-4e2bc880672f/resourceGroups/rgDEV/providers/Microsoft.Cache/redis/redis2f94d61f/listKeys: autorest/azure: Service returned an error. Status=404 Code="ResourceNotFound" Message="The Resource 'Microsoft.Cache/Redis/redis2f94d61f' under resource group 'rgDEV' was not found. For more details please go to <https://aka.ms/ARMResourceNotFoundFix>"
        at Object.callback (C:\Projects\Deon\infrastructure\azureresources\node_modules\@pulumi\pulumi\runtime\invoke.js:139:33)
        at Object.onReceiveStatus (C:\Projects\Deon\infrastructure\azureresources\node_modules\@grpc\grpc-js\src\client.ts:338:26)
        at Object.onReceiveStatus (C:\Projects\Deon\infrastructure\azureresources\node_modules\@grpc\grpc-js\src\client-interceptors.ts:426:34)
        at Object.onReceiveStatus (C:\Projects\Deon\infrastructure\azureresources\node_modules\@grpc\grpc-js\src\client-interceptors.ts:389:48)
        at C:\Projects\Deon\infrastructure\azureresources\node_modules\@grpc\grpc-js\src\call-stream.ts:276:24
        at processTicksAndRejections (internal/process/task_queues.js:79:11)

The code for that passage is

function createRedis() : azure.types.input.web.NameValuePairArgs[]{
    var cache= new redis.Redis("redis", {
        resourceGroupName,
        enableNonSslPort: true,
        minimumTlsVersion: redis.TlsVersion.TlsVersion_1_2,
        sku: {
            name: "Basic",
            family: "C",
            capacity: cfg.requireNumber("Redis.Size")
        }
    });
    
    const keys= pulumi.all([resourceGroupName, cache.name])
                 .apply(([resourceGroupName, name])=>redis.listRedisKeys({resourceGroupName, name}))
    const connectionString= pulumi.interpolate `${cache.hostName}:6380,password=${keys.primaryKey},ssl=True,abortConnect=False`;
    return [
        {
            name: "Redis:ConnectionString",
            value: connectionString
        },
    ];
}

Now what I don't get is: of course when doing preview, the redis instance isn't there yet. But I kinda expected that Pulumi somehow deals with this in the background, maybe not calling apply if cache.Name is not available yet. Also, I think I didn't have the problem before - but that might just be because I called it incrementally, never on a completely clean slate. Note the same thing happens when I execute

pulumi up

when it's in the preview stage. So this is currently a big blocker for me. Any ideas, anyone?

You likely need to put the

native:cache:listRedisKeys

call inside an apply, similar to https://github.com/pulumi/templates/blob/master/azure-typescript/index.ts#L18-L19

but it is in an apply call, look at the code - or am I missing something?

Oh, sorry, I didn’t read the code correctly… let me try it locally.

thx!

Hmm… this preview works for me

import * as pulumi from "@pulumi/pulumi";
import * as resources from "@pulumi/azure-native/resources";
import * as redis from "@pulumi/azure-native/cache";

const resourceGroup = new resources.ResourceGroup("rg");

var cache= new redis.Redis("redis", {
    resourceGroupName: resourceGroup.name,
    enableNonSslPort: true,
    minimumTlsVersion: redis.TlsVersion.TlsVersion_1_2,
    sku: {
        name: "Basic",
        family: "C",
        capacity: 1
    }
});
const keys= pulumi.all([resourceGroup.name, cache.name])
             .apply(([resourceGroupName, name])=>redis.listRedisKeys({resourceGroupName, name}))
export const connectionString= pulumi.interpolate `${cache.hostName}:6380,password=${keys.primaryKey},ssl=True,abortConnect=False`;

could it be because I do the `const connectionstring =...`outside the apply? if yes, then how exactly would I rewrite that?

No, interpolate does the right thing

hmm. how can I dig further?

Can you run my code in isolation and see you get the same?

could it matter that the resourcegroup is not being created by pulumi? because that I changed, I now supply it's name via config. (Background: i need to create and configure a b2c instance outside of pulumi because what I need to there doesn't work within.)

Aha! Yes, I reproduced your error with an existing RG.

ah

The workaround is to change

all

to this:

const keys= pulumi.all([resourceGroup.name, cache.name, cache.id])

ah, thx for the workaround

yes, https://github.com/pulumi/pulumi-azure-native/issues

ok

please mention the pre-existing resource group

yes, you don’t have to do that