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

Build path nodes off a property config to be able to differentiate infrastructure #29

Open
ccloes opened this issue Dec 13, 2023 · 1 comment

Comments

@ccloes
Copy link
Collaborator

ccloes commented Dec 13, 2023

Given an endpoint and path, we want to be able to traverse where a path leads to different infrastructure. Right now, we link all "outbound" paths from the same endpoint but don't know what "path" it takes to get there. We would like to have that path data as well.

hosted_in_akamai.mycompany.com/path1 -> reverse proxy 1 (one set of infra)
hosted_in_akamai.mycompany.com/path2 -> reverse proxy 2 (another different set of infra)

@ccloes
Copy link
Collaborator Author

ccloes commented Feb 14, 2024

There was discussion on this where the paths will be represented as RELATIONSHIPS from the AkamaiProperty node to the Origin Node.

Maybe we should create an Arrows.app schema representation of this I attempted to start one here:
Schema discussion

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

No branches or pull requests

1 participant