Skip to content

chore: Build against Connect v1.0.0-preview.28 - #31

Draft
kprabhak wants to merge 1 commit into
feat/masque-connectfrom
chore/connect-preview-28
Draft

kprabhak wants to merge 1 commit into
feat/masque-connectfrom
chore/connect-preview-28

Conversation

@kprabhak

Copy link
Copy Markdown

Summary

The gateway image builds against Connect v1.0.0-preview.14-3, while Connect's current release is preview 28, and the CONNECT-IP code the gateway uses is identical in both.

This raises the pinned Connect revision to the preview 28 release.

A gateway configured to forward UDP now uses the standard CONNECT-UDP form, which Connectors older than preview 16 cannot answer. The gateway Connect deploys forwards no UDP and is unaffected.

Test plan

  • The gateway builds and its tests pass against preview 28
  • TCP and UDP forwarding work to a preview 28 Connector

Related to datum-cloud/enhancements#883 and datum-cloud/enhancements#916

The image builds against Connect v1.0.0-preview.14-3, while Connect's
current release is preview 28. The CONNECT-IP code the gateway uses
is the same in both, and the gateway builds and passes its tests
against preview 28 with no source change.

One behaviour changes, for a gateway configured to forward UDP. From
preview 16, the transport sends UDP requests to a Connector in the
standard CONNECT-UDP form and expects the Connector to confirm the
Capsule Protocol. A Connector older than preview 16 does not, so UDP
forwarding to it fails. TCP forwarding is unchanged, and a gateway
with no UDP forwards, such as the one Connect deploys, is unaffected.

Raise CONNECT_REV to the preview 28 release commit.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant