Izilungiselelo ze-proxy ze-Service Bus trigger ku-Azure Functions ku-host.json

Sebenzisa i-webProxy ye-host.json ye-Service Bus extension 5.x ne-amqpWebSockets, esikhundleni sokuhlela enye i-ServiceBusClient kukhodi ye-function.

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

Hlanganisa lokhu ekuhlelweni kwe-Functions host okukhona. I-binding extension yakha i-client ye-trigger; i-client eyakhiwe ngokwahlukile kukhodi ye-function ayiyithathi indawo.

I-extension 5.x isekela webProxy ne amqpWebSockets, hhayi amqpTcp. Gcina i-namespace/authentication ekuhlelweni kwe-Service Bus okukhona. Nge-namespace yomphakathi ye-Service Bus lapho abalamuli bomphakathi bavunyelwe, uhlu lwe-proxy lwe-HTTP luhlinzeka ngabazongenela i-webProxy URL engena-akhawunti.

Okulingana ezilungiselelweni zohlelo lokusebenza yile:

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

Sebenzisa leyo mpetho yamaphuzu amabili angaphansi ezilungiselelweni zemvelo, noma okufakiwe efayeleni local.settings.json, isigaba Values, sokuthuthukiswa kwendawo. Lezi zilungiselelo ze-host, hhayi izinkambu ze-connection string.

Qondanisa nesizukulwane se-extension esifakiwe. I-client ye-HTTP noma ye-Service Bus ezimele yese-benzi elihlukanisiwe isadinga indlela yayo.

Izihloko ezihlobene