freeipa/install
Gabe 1e91ef33b5 custodia: ipa-upgrade failed on replica
- Add 73-custodia.update to install/updates/Makefile.am

https://fedorahosted.org/freeipa/ticket/5374

Reviewed-By: Martin Basti <mbasti@redhat.com>
2015-11-05 11:46:48 +01:00
..
certmonger Alias "unicode" to "str" under Python 3 2015-09-17 11:08:43 +02:00
conf Add ipa-custodia service 2015-10-15 14:24:33 +02:00
ffextension webui: append network.negotiate-auth.trusted-uris 2014-09-11 09:41:51 +02:00
html webui: use manual Firefox configuration for Firefox >= 40 2015-09-21 12:57:25 +02:00
migration Replace dict.has_key with the 'in' operator 2015-08-12 18:17:23 +02:00
oddjob Alias "unicode" to "str" under Python 3 2015-09-17 11:08:43 +02:00
po fix broken translations after last po update 2015-11-02 19:33:07 +01:00
restart_scripts install: always export KRA agent PEM file 2015-10-08 13:42:58 +02:00
share Allow to setup the CA when promoting a replica 2015-10-15 14:24:33 +02:00
tools Incomplete ports for IPA AD Trust 2015-11-05 11:04:29 +01:00
ui Fixes disappearing automember expressions 2015-10-14 12:31:51 +02:00
updates custodia: ipa-upgrade failed on replica 2015-11-05 11:46:48 +01:00
wsgi Modernize 'except' clauses 2015-08-12 18:17:23 +02:00
configure.ac trusts: add support for one-way trust and switch to it by default 2015-07-08 01:56:52 +02:00
Makefile.am trusts: add support for one-way trust and switch to it by default 2015-07-08 01:56:52 +02:00
README.schema Add some basic rules for adding new schema 2010-08-27 13:40:37 -04:00

Ground rules on adding new schema

Brand new schema, particularly when written specifically for IPA, should be
added in share/*.ldif. Any new files need to be explicitly loaded in
ipaserver/install/dsinstance.py. These simply get copied directly into
the new instance schema directory.

Existing schema (e.g. in an LDAP draft) may either be added as a separate
ldif in share or as an update in the updates directory. The advantage of
adding the schema as an update is if 389-ds ever adds the schema then the
installation won't fail due to existing schema failing to load during
bootstrap.

If the new schema requires a new container then this should be added
to install/bootstrap-template.ldif.