Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • fusiondirectory fusiondirectory
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 33
    • Issues 33
    • List
    • Boards
    • Service Desk
    • Milestones
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Terraform modules
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • fusiondirectoryfusiondirectory
  • fusiondirectoryfusiondirectory
  • Issues
  • #3879
Closed
Open
Issue created Jun 17, 2015 by bmortier@bmortierMaintainer

we need an option into fusiondirectory-insert-schema to empty a schema

Hello,

as we cannot remove a schema from openldap cn=config backedn we need an option to empty a schema in case it conflict with other schema update.

An example for this is for example the dasboard schema that as been migrated to core and we cannot get to two installed

Cheers

(from redmine: issue id 3879, created on 2015-06-17, closed on 2015-06-23)

  • Changesets:
    • Revision ed695a9a by Côme Chilliet on 2015-06-18T11:13:42.000Z:
Fixes #3879 we need an option into fusiondirectory-insert-schema to empty a schema
  • Revision 801585bd by Côme Chilliet on 2015-06-18T11:13:57.000Z:
Fixes #3879 we need an option into fusiondirectory-insert-schema to empty a schema
  • Revision c6fa3bfb by Côme Chilliet on 2015-06-18T12:18:28.000Z:
Fixes #3879 we need an option into fusiondirectory-insert-schema to empty a schema

Conflicts:
	contrib/bin/fusiondirectory-insert-schema
  • Custom Fields:
    • Bug in version: 1.0.8.7
  • Uploads:
    • 0001-Fixes-3879-we-need-an-option-into-fusiondirectory-in.patch
Assignee
Assign to
Time tracking