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

Autorequire previous sibling object #1

Closed
bodgit opened this issue Jan 16, 2015 · 0 comments
Closed

Autorequire previous sibling object #1

bodgit opened this issue Jan 16, 2015 · 0 comments
Assignees
Labels

Comments

@bodgit
Copy link
Owner

bodgit commented Jan 16, 2015

Currently we autorequire parent objects so in the case of cn=foo,dc=example,dc=com & dc=example,dc=com the latter gets required by the former so that it can be potentially created first in the DIT.

However, thanks to OpenLDAP's {x} ordering notation, if we have cn={1}foo,dc=example,dc=com & cn={2}bar,dc=example,dc=com there also needs to be a relationship to create cn={1}foo before cn={2}bar otherwise OpenLDAP will helpfully reorder them to be cn={1}bar and cn={2}foo if they happen to be created in that order. The {x} is seemingly ignored for creation but required for modification or deletion to accurately target the right object.

It should be possible to extend the autorequire logic to create this relationship if both siblings are managed by Puppet.

@bodgit bodgit added the bug label Jan 16, 2015
@bodgit bodgit self-assigned this Jan 16, 2015
bodgit added a commit that referenced this issue Jan 25, 2015
Also use #select instead of #reject with a ! condition, duh
@bodgit bodgit closed this as completed Jan 25, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant