Currently, the extension arbitrarily decides that the first bound port of the tye process found is the dashboard API endpoint. However, if ingress is enabled, the tye process may bind additional ports. If those ports are found before the actual dashboard API endpoint, the extension will fail to show the application.
This change has the Tye process provider check each port associated with a tye process to verify one of them as the dashboard API endpoint (by calling the "get endpoints" endpoint).
Currently, the extension arbitrarily decides that the first bound port of the
tyeprocess found is the dashboard API endpoint. However, if ingress is enabled, thetyeprocess may bind additional ports. If those ports are found before the actual dashboard API endpoint, the extension will fail to show the application.This change has the Tye process provider check each port associated with a
tyeprocess to verify one of them as the dashboard API endpoint (by calling the "get endpoints" endpoint).Resolves #125.