Add ConnectionType enum (STANDARD, TEST, MONITORING) - #57
Open
bpescato-amazon wants to merge 2 commits into
Open
Add ConnectionType enum (STANDARD, TEST, MONITORING)#57bpescato-amazon wants to merge 2 commits into
bpescato-amazon wants to merge 2 commits into
Conversation
Introduce a ConnectionType enum to distinguish between ordinary customer connections and special-purpose connections used for testing or monitoring. The new optional 'connectionType' field on Connection defaults to CONNECTION_TYPE_STANDARD when not specified. Connection types: - STANDARD: ordinary customer connections - TEST: reserved for provider dev teams; may use sub-minimum bandwidths, does not count against capacity, partners may enforce a small quota - MONITORING: reserved for active monitoring sessions; may use small bandwidths, does not count against capacity, limited to 1 per interconnect to enable monitoring across all underlying links
dkarwowski
reviewed
Jul 29, 2026
| size (e.g. 50 Mbps). Bandwidth consumed by test connections must not | ||
| count against interconnect or environment capacity totals. Partners may | ||
| enforce a small quota on the number of active test connections. | ||
| CONNECTION_TYPE_MONITORING - Monitoring connections are reserved for |
Collaborator
There was a problem hiding this comment.
Are we expecting any specific routing behavior from the monitoring connections (i.e. the reflector attachments) or just standard routing?
If we're expecting any special routing config here we probably want to document how it would work differently.
Contributor
Author
There was a problem hiding this comment.
I do think that the expectation of the MONITORING type is that any special routing that local provider must do to enable the agreed upon monitoring for the remote provider should be present.
I don't know if we want to distinctly document exactly what that should be per the API, as each provider may have differing requirements here.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Introduce a ConnectionType enum to distinguish between ordinary customer connections and special-purpose connections used for testing or monitoring.
The new optional 'connectionType' field on Connection defaults to CONNECTION_TYPE_STANDARD when not specified.
Connection types:
Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.