#50534 UI - editing custom schema is problematic
Closed: fixed 4 months ago by mreynolds. Opened 4 months ago by mreynolds.

Issue Description

Editing custom schema actually does a delete/add. This causes issues in the UI and CLI. This was partially fixed in https://pagure.io/389-ds-base/issue/50507 - which needs to be back ported to 1.4.0.

In the CLI we need to change the "edit" subcommand to "replace" so it is clear what it is actually doing.


Backport schema fixes to 1.4.0:

320a1b6..f3c18b1 389-ds-base-1.4.0 -> 389-ds-base-1.4.0

Next, change CLI to use "replace" over "edit"

Metadata Update from @mreynolds:
- Custom field origin adjusted to None
- Custom field reviewstatus adjusted to None

4 months ago

Commit b8c6485 relates to this ticket

f3c18b1..a14dd18 389-ds-base-1.4.0 -> 389-ds-base-1.4.0

Metadata Update from @mreynolds:
- Issue close_status updated to: fixed
- Issue status updated to: Closed (was: Open)

4 months ago

Login to comment on this ticket.

Metadata
Related Pull Requests