Keep Azure IoT Edge Proxy Settings in Deployment Manifests

Bootstrap connectivity can disappear when a later manifest replaces edgeAgent/edgeHub environment without its proxy values.

When a deployment replaces runtime definitions, retain the proxy in both modules. For edgeAgent, merge:

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

Keep this under edgeAgent desired properties/systemModules with the actual definitions. Preserve images, settings and other environment entries. edgeHub also needs its https_proxy; the shown UpstreamProtocol preserves the agent's AmqpWs startup choice.

AMQP over WebSockets is required when the intermediary blocks native AMQP. The HTTP URL describes the listener even though the service uses TLS.

Carry the values into future manifests. Removing edgeAgent's route can prevent it receiving the very deployment meant to repair it.

The container engine's image pulls, identity service and Edge daemon remain separate consumers. In EFLOW they run in the Linux VM, so a Windows-host setting alone does not configure them. User modules likewise need inputs their own clients support.

Mikanda mikatakata