-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
124 all subnets grouping #136
Conversation
…string so that (among others) grouping can be reused
6db386c
to
5ad89a8
Compare
solves #124 |
sub2-1-ky => sub2-2-ky : All Connections | ||
sub2-2-ky => sub2-1-ky : All Connections | ||
|
||
connections are stateful unless marked with * |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we do not yet have any implemented computation of whether subnets connectivity is stateful.
We should remove that comment , and have another issue to handle stateful computation for this as well,
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Opened #138 (next in my todos) as well as ugly WA code that will be removed once the issue is solved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
We have to consider if EndpointElem
is really required in the code, given that we already have VPCResourceIntf
. This may allow us to reduce code duplication, as Node
also embeds VPCResourceIntf
. This can wait for now, but maybe open an issue for that...
#141 |
No description provided.