Replies: 1 comment
|
I asked the same question on StackOverflow, so maybe it will help someone https://stackoverflow.com/questions/79598787/azure-function-deployment-with-azure-signalr-service-in-pulumi |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
I have a Pulumi deployment that deploys Azure function app. That works without issues. Due to new requirement I need to now add Azure SignalR Service that will communicate with the existing Azure Function app., However I encountered a bit of chicken and egg problem:
The Azure Function app needs connection string to Azure SignalR Service and Azure SignalR Service needs upstream configuration to Azure Function app.
So if I have Azure Function app resource first and Azure SignalR Service resource second, then in Azure Function app I can not use Azure SignalR Service's connection string.
On the other hand if I have Azure SignalR Service resource first and Azure Function app resource second, then in Azure SignalR Service I can not use Azure Function app's hostname for upstream configuration.
The approach I'm currently considering is to have Function app resource first (as this already exists), which will allow me to use its hostname in SignaR Service resource upstream configuration afterwards and then after I have also SignalR Service resource use its connection string to update Function app settings. Is something like that possible? Or what is the reccommended approach to solve such issue?
All reactions