Update connector endpoints to use the new reactor address

[kiahna-tucker]

Last Updated: Sept. 25, 2024

---

The connector endpoint displayed on the Overview tab of a task Details page needs to use the new reactor address instead of that returned by the gateway_auth_token RPC.

Below are the base requirements for this feature:

• Update connector endpoints to use the reactor address of the matched data-plane specified by the reactor_address column of the live_specs_ext view.

Dependencies

Last Updated: Sept. 25, 2024

• [x] Database support. The live_specs_ext view needs to be extended to include the reactor_address of the matched data-plane (i.e., value of the data_plane_id column of the live_specs table).

Additional Comments

• The control-plane, task authorization API will be slow to return when a task is first created because it must fetch a new snapshot to observe the task. An alternative would be to source the address from the reactor_address column of the matched data-plane. If the alternative approach is preferable, the reactor_address column in the data_planes table would need to be added to the live_specs_ext view.

• For client development, the useShardEndpoints and useScopedGatewayAuthToken hooks are the primary points of interest.

[kiahna-tucker]

A requirement for this feature was not communicated before this feature was released:

• Rewrite the reactor address for tasks using the legacy data-plane so that it is recognized by the data-plane gateway. The task authorization API will return an internal service address which is unreachable.

This change will be bundled in PR 1289 which is the complete solution for issue 1274 that has the same requirement. Noting this in this issue for completeness.

References

Code

• Reactor address modifying routine. The routine the agent API uses to detect and re-write reactor addresses when used in an external context (e.g., an exposed connector endpoint).