Ku hay instaqdka proxy-ga Azure IoT Edge ee manifest-yada diritaanka

Xiriirka bilowga ayaa lumi kara marka manifest dambe uu beddelo bey'adda edgeAgent/edgeHub iyada oo aan lahayn qiyamka proxy-ga.

Marka diritaan uu beddelo qeexitaannada wakhtiga socodka, ku hay proxy-ga labada module. edgeAgent waxaad isku daraysaa:

"env": {
  "https_proxy": {
    "value": "http://proxy.example:8080"
  },
  "UpstreamProtocol": {
    "value": "AmqpWs"
  }
}

Tan ku hay edgeAgent desired properties/systemModules oo la socda qeexitaannada dhabta ah. Ilaali sawirada, dejinta iyo gelitaannada kale ee bey'adda. edgeHub sidoo kale wuxuu u baahan yahay https_proxy; UpstreamProtocol la muujiyay wuxuu ilaaliyaa doorashada AmqpWs ee bilowga wakiilka.

AMQP iyada oo loo marayo WebSockets ayaa loo baahan yahay marka dhexdhexaadiyuhu xannibo AMQP asalka ah. HTTP URL waxay qeexdaa dhegeysanaha inkastoo adeeggu isticmaalo TLS.

Qiyamka u gudbi manifest-yada mustaqbalka. Ka saarista dariiqa edgeAgent waxay ka hor istaagi kartaa helitaanka diritaanka loogu talagalay inuu ku hagaajiyo.

Soo jiidashada sawirada mishiinka konteenarada, adeegga aqoonsiga iyo Edge daemon waxay ahaanayaan macaamiil gooni ah. EFLOW waxay ku shaqeeyaan Linux VM, sidaas darteed dejinta kaliya ee martigeliyaha Windows ma habeeyso iyaga. Module-yada isticmaalaha sidoo kale waxay u baahan yihiin gelitaanno ay taageeraan macaamiishooda.

Maqaallo la xiriira