This message was deleted.

UPDATE: So the creation of the DictionaryID is only done when the resource is actually deployed and will not be available like this during

pulumi up

. I fixed this issue by using

dependsOn: [service]

when defining my dictionaryItems.

const MyComputeService = new ServiceCompute(...)

new fastly.ServiceDictionaryItems('MyDictionary', {
    serviceId: service.id,
    dictionaryId: MyComputeService.dictionaries.apply(d => d?.[0].dictionaryId || '1234'),
    items: {
        'item1': config.require('item1').toString(),
        'item2': config.require('item2').toString()
    }
}, {dependsOn: [MyComputeService]})