Bug 30612 – Show dependent objects when deleting

Bug 30612 - Show dependent objects when deleting


Summary:	Show dependent objects when deleting

Status:	REOPENED

Product:	UCS
Classification:	Unclassified
Component:	UMC - Domain management (Generic)
Version:	UCS 4.4
Hardware:	Other Linux

Importance:	P5 normal with 9 votes (vote)
Target Milestone:	---
Assigned To:	UMC maintainers
QA Contact:

URL:
Keywords:

Duplicates:	29671 32013 (view as bug list)
Depends on:	26062
Blocks:
	Show dependency tree / graph

Reported:	2013-02-28 12:54 CET by Philipp Hahn
Modified:	2019-02-04 11:01 CET (History)
CC List:	3 users (show)

See Also:	25019 25449 32046
What kind of report is it?:	Feature Request
What type of bug is this?:	---
Who will be affected by this bug?:	---
How will those affected feel about the bug?:	---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):	Usability
Max CVSS v3 score:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Philipp Hahn

2013-02-28 12:54:13 CET

When I delete an object, I get asked for "Zugehörige Objekte löschen".
This question can't be answered with confidence, since it's unknown which objects will be deleted.
Since Bug #26062 I'm reluctant to delete things without knowing what exactly will be deleted, since I've lost at least two times the full content of LDAP.

Comment 1 Dirk Wiesenthal

2013-02-28 16:03:41 CET

*** Bug 29671 has been marked as a duplicate of this bug. ***

Comment 2 Dirk Wiesenthal

2013-07-19 12:00:08 CEST

*** Bug 32013 has been marked as a duplicate of this bug. ***

Comment 3 Florian Best

2016-10-21 15:01:27 CEST

In the UMC-UDM module I created the base for a generic handling of referencing-objects UDM_Module.get_references(dn).

My idea for this was that a UDM object gets a pseudo property with a list of references.
These references may of various types (e.g. 
With this one can add generic <link>-relations between objects - which can also be shown (and opened via a click on a button) in UMC. This exists already for the referenced policies.

$references$ = [{
    'type': 'ldap-object',
    'dn': 'dn=foo,dc=base',
    'objectType': 'foo/bar',
    'icon': '',
    'label': ''
} , {
}]

Types may be: complete object, entry in a attribute/property of a object, entry in PKGDB, whatever.

Comment 4 Philipp Hahn

2017-01-19 15:40:10 CET

(In reply to Florian Best from comment #3)
> In the UMC-UDM module I created the base for a generic handling of
> referencing-objects UDM_Module.get_references(dn).
...
> Types may be: complete object, entry in a attribute/property of a object,
> entry in PKGDB, whatever.

This would be useful for Bug #32046 to link UDM-computer-object to UVMM-VM (and vis-versa)

Comment 5 Philipp Hahn

2017-01-19 15:42:59 CET

(In reply to Philipp Hahn from comment #4)
> (In reply to Florian Best from comment #3)
> > In the UMC-UDM module I created the base for a generic handling of
> > referencing-objects UDM_Module.get_references(dn).
> ...
> > Types may be: complete object, entry in a attribute/property of a object,
> > entry in PKGDB, whatever.
> 
> This would be useful for Bug #32046 to link UDM-computer-object to UVMM-VM
> (and vis-versa)

Wrong Bug, correct is Bug #25449

Comment 6 Stefan Gohmann

2019-01-03 07:19:25 CET

This issue has been filled against UCS 4.1. The maintenance with bug and security fixes for UCS 4.1 has ended on 5st of April 2018.

Customers still on UCS 4.1 are encouraged to update to UCS 4.3. Please contact
your partner or Univention for any questions.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or simply reopen the issue. In this case please provide detailed information on how this issue is affecting you.