This repository has been archived by the owner on Aug 16, 2022. It is now read-only.
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.
Lag schema: https://pkg.go.dev/github.com/aws/aws-sdk-go-v2/service/[email protected]/types#Lag
As we are already capturing DirectConnect Connections in a separate table, I opted to not resave that data, and instead just save the connectionIds in a StringArray.
Connection -> Lag is a Many:1 relationship, but not all connections necessarily have a Lag. Perhaps this is a scenario where we could introduce nullable FKs or something like that?