You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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 havecn={1}foo,dc=example,dc=com
&cn={2}bar,dc=example,dc=com
there also needs to be a relationship to createcn={1}foo
beforecn={2}bar
otherwise OpenLDAP will helpfully reorder them to becn={1}bar
andcn={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.
The text was updated successfully, but these errors were encountered: