Saitunan wakili na Service Bus trigger a Azure Functions a cikin host.json

Yi amfani da webProxy na host.json na fadada Service Bus 5.x tare da amqpWebSockets, maimakon daidaita wani ServiceBusClient a cikin lambar aiki.

{
  "version": "2.0",
  "extensions": {
    "serviceBus": {
      "transportType": "amqpWebSockets",
      "webProxy": "http://proxy.example:8080"
    }
  }
}

Haɗa wannan cikin tsarin host na Functions da ke akwai. Fadadar ɗaure tana ƙirƙirar abokin ciniki na trigger; abokin ciniki da aka gina daban a cikin lambar aiki ba ya maye gurbinsa.

Fadada 5.x tana goyan bayan webProxy tare da amqpWebSockets, ba amqpTcp ba. Ka riƙe namespace/authentication a cikin saitunan haɗin Service Bus da ke akwai. Don namespace na Service Bus na jama'a inda aka yarda da masu shiga tsakani na jama'a, jerin wakilan HTTP yana ba da 'yan takara don URL na webProxy mara asusu.

Masanin saitunan aikace-aikacen sune:

AzureFunctionsJobHost__extensions__serviceBus__transportType=amqpWebSockets
AzureFunctionsJobHost__extensions__serviceBus__webProxy=http://proxy.example:8080

Yi amfani da wannan matakan jeri mai layi biyu a cikin saitunan muhalli, ko shigarwa a cikin fayil ɗin local.settings.json, sashin Values, don ci gaban gida. Saitunan host ne, ba filayen igiyar haɗi ba.

Daidaita da ƙarni na fadada da aka shigar. Abokin ciniki na HTTP ko Service Bus mai zaman kansa na ma'aikacin keɓe har yanzu yana buƙatar hanyarsa.

Labarai masu alaƙa