/usr/share/perl5/cipux-storage.perl.pod is in libcipux-storage-perl 3.4.0.2-6.1.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 | =pod
=head1 cipux-storage.perl
The CipUX storage layer comes with two configuration files. One for configuring
basic values. This called typically cipux-storage.perl. The other holds the
access data for the storage backend. Mostly called cipux-access.perl.
This document describes cipux-storage.perl.
Example:
$cfg = {
'structure' => {
'cipux_ldap_orga_node' => {
desc => 'access all CipUX LDAP orga nodes',
struc_rdn => '',
dn_attr => 'ou',
filter => '&(ou=?)(objectClass=cipuxLdapOrgaNode)',
},
'cipux_account.user' => {
desc => 'access all CipUX user account user nodes',
struc_rdn => 'ou=User',
dn_attr => 'uid',
filter => '&(uid=?)(objectClass=cipuxAccount)(cipuxIsAccount=TRUE)',
},
},
};
=head2 $cfg
Hold the storage node structural data.
At the first level it has a scope. The scope "debian" is used for the default
storage structure.
On the next level the single data nodes are defined.
I<desc>
Some short description about the node and its data.
I<struc_rdn>
Organizational node under which the data is stored.
struc_rdn + ou=CipUX + LDAP suffix.
Example:
ou=Task,ou=CipUX,dc=nodomain
will gives us ou=Task as struc_rdn
struc_rdn => 'ou=Task',
I<dn_attr>
The first attribute of the dn line. This should correspond to the filter
section.
I<filter>
This filter will be applied to get the data.
=cut
|