We have successfully implemented pulumi azure next...
# azure
b
We have successfully implemented pulumi azure nextgen with our core infrastructure, but when running it in azure devops pipeline it fails when trying to lookup signalr keys. Is this an error in pulumi or in some devops setting? and which? Stacktrace attached… Thank you in advance!
Copy code
Grpc.Core.RpcException: Status(StatusCode="Unknown", Detail="invocation of azure-nextgen:signalrservice/latest:listSignalRKeys returned an error: request failed /subscriptions/5d5f4691-723c-462e-b620-e4219f22ee8a/resourceGroups/rg-nuuday-troubleticket-development/providers/Microsoft.SignalRService/signalR/signalr-service-waxfpu/listKeys: autorest/azure: Service returned an error. Status=404 Code="ResourceNotFound" Message="The Resource 'Microsoft.SignalRService/SignalR/signalr-service-waxfpu' under resource group 'rg-nuuday-troubleticket-development' was not found. For more details please go to <https://aka.ms/ARMResourceNotFoundFix>"", DebugException="Grpc.Core.Internal.CoreErrorDetailException: {"created":"@1610621210.259509913","description":"Error received from peer ipv4:127.0.0.1:40251","file":"/var/local/git/grpc/src/core/lib/surface/call.cc","file_line":1063,"grpc_message":"invocation of azure-nextgen:signalrservice/latest:listSignalRKeys returned an error: request failed /subscriptions/5d5f4691-723c-462e-b620-e4219f22ee8a/resourceGroups/rg-nuuday-troubleticket-development/providers/Microsoft.SignalRService/signalR/signalr-service-waxfpu/listKeys: autorest/azure: Service returned an error. Status=404 Code="ResourceNotFound" Message="The Resource 'Microsoft.SignalRService/SignalR/signalr-service-waxfpu' under resource group 'rg-nuuday-troubleticket-development' was not found. For more details please go to
t
Are you calling
listSignalRKeys
from within an
Apply
that depends on the resource?
b
will try to refactor, thanks
t
This approach is a bit tricky to write but it ensures a proper dependency flow
🙏 1
b
Our error was due to devops azure access restrictions but nice to know that we should follow that approach