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.

Sign up for GitHub

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

Jump to bottom

Build Org hierarchy from parents, not children #18

Closed
rmc3 opened this issue May 7, 2018 · 1 comment
Closed

Build Org hierarchy from parents, not children #18

rmc3 opened this issue May 7, 2018 · 1 comment
Labels
backlog MVP

Comments

@rmc3
Copy link
Contributor

rmc3 commented May 7, 2018

The Organization hierarchy should be built by following parents to their children, rather than the reverse. This mirrors the way that the AWS Organizations API works. Each Orgunit should have a list of children, if any. The hierarchy must determine which Orgunits are not the children of any other Orgunits to determine which Orgunits are at the top of the hierarchy. Detection of cycles in hierarchy paths should be preserved.
@rmc3
Copy link
Contributor Author

rmc3 commented May 7, 2018

This has been implemented.

@rmc3 rmc3 closed this as completed May 7, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
backlog MVP
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@rmc3