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

new check: using coordinating as leaf #110

Closed
trel opened this issue Nov 13, 2021 · 5 comments
Closed

new check: using coordinating as leaf #110

trel opened this issue Nov 13, 2021 · 5 comments
Assignees
Labels
enhancement New feature or request
Milestone

Comments

@trel
Copy link
Member

trel commented Nov 13, 2021

are any replication, random, passthru resources currently leaf resources in existing hierarchies

@trel
Copy link
Member Author

trel commented Jun 19, 2023

similar to #111

@trel trel added this to the 0.4.0 milestone Jun 19, 2023
@ganning127
Copy link
Contributor

ganning127 commented Jun 21, 2023

Is this issue just saying that if replication, random, passthru resources have any children, then the check fails? If so, that would make this issue very similar to the already open PR you mentioned

@trel
Copy link
Member Author

trel commented Jun 21, 2023

No, not quite... resources of those types listed above... should not be last / leaf ... aka, they should ALWAYS have at least one child.

@ganning127
Copy link
Contributor

ganning127 commented Jun 21, 2023

Shoot yep, I forgot to type the "don't" before "have" lol. But isn't what you're saying about how these coordinating resources should always have at least one child already in #162?

@trel
Copy link
Member Author

trel commented Jun 21, 2023

ah, yes - you can point that coordinating commit / work to this issue.

ganning127 added a commit to ganning127/irods_client_zone_management_tool that referenced this issue Jun 23, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Development

No branches or pull requests

2 participants