Skip to content
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

Enhance Route Tables reporting #24

Closed
patrykorwat opened this issue May 23, 2020 · 2 comments · Fixed by #48
Closed

Enhance Route Tables reporting #24

patrykorwat opened this issue May 23, 2020 · 2 comments · Fixed by #48
Assignees

Comments

@patrykorwat
Copy link
Member

Currently a route table is reported to be directly associated with a VPC but in practice, the relationship is much more complex, with the tables being associated with subnets. The tool should detect that relationship and report it properly.
There is also a concept of a default table, that should be reported.

@leandrodamascena leandrodamascena pinned this issue Jun 2, 2020
@patrykorwat
Copy link
Member Author

patrykorwat commented Jun 3, 2020

The initial idea can be enhanced to detect route table associations to subnets to:

  1. Be able to create a subnets groups: private and public
  2. Trick diagrams library to aggregate multiple edges that that to all subnets within a cluster to have one connection to such private/public cluster

The outcome will be simpler diagrams. For the change, the fdp graphviz engine must be used.

patrykorwat added a commit to patrykorwat/aws-network-discovery that referenced this issue Jun 3, 2020
@patrykorwat
Copy link
Member Author

Blocked by mingrammer/diagrams#17.

For the time being, we can aggregate the multiple subnets into one (perhaps represented with a bigger icon), in order to make the diagram cleaner.

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 a pull request may close this issue.

1 participant