mirror of
https://salsa.debian.org/freeipa-team/freeipa.git
synced 2025-02-25 18:55:28 -06:00
b43c2f8ab4
Details facet for user, hosts, service, user override entities require complex reload as they gather information from multiple sources - e.g. all of them do cert-find. On update only $entity-mod is execute and its result doesn't have all information required for refresh of the page therefore some fields are missing or empty. This patch modifies the facets to do full refresh instead of default load and thus the pages will have all required info. https://pagure.io/freeipa/issue/5776 Reviewed-By: Felipe Volpone <felipevolpone@gmail.com> Reviewed-By: Michal Reznik <mreznik@redhat.com> |
||
|---|---|---|
| .. | ||
| certmonger | ||
| html | ||
| migration | ||
| oddjob | ||
| restart_scripts | ||
| share | ||
| tools | ||
| ui | ||
| updates | ||
| wsgi | ||
| Makefile.am | ||
| README.schema | ||
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.